# Nodes randomly not getting latest cluster state

**URL:** https://discuss.elastic.co/t/nodes-randomly-not-getting-latest-cluster-state/19945
**Category:** Elasticsearch
**Created:** [September 24, 2014, 2:09pm UTC](https://discuss.elastic.co/t/nodes-randomly-not-getting-latest-cluster-state/19945 "2014-09-24T14:09:52Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![srijan55](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@srijan55](https://discuss.elastic.co/u/srijan55)
#### Post date: [September 24, 2014, 2:09pm UTC](https://discuss.elastic.co/t/nodes-randomly-not-getting-latest-cluster-state/19945/1 "2014-09-24T14:09:52Z")

</div>

We have run into this weird problem in our cluster deployment where at random nodes don't recieve the latest cluster state, and when this happens, they just lie there without actually doing anything with the cluster, this fails the scenarios where we are either indexing or searching from the shards on the node. The cluster (other nodes or master) still report the state is healthy, but the only mitigation to let the things moving on the node, which we have found is to recycle the elastic search service on the node.  
So far there has been no co-relation between any activity and this problem, any hints would be helpful.

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 25, 2014, 10:03pm UTC](https://discuss.elastic.co/t/nodes-randomly-not-getting-latest-cluster-state/19945/2 "2014-09-25T22:03:58Z")

</div>

Checked your logs?

What ES and java version, how many nodes (data and master) and how much  
data do you store (doc, size and index counts).

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 25 September 2014 00:09, srijan55 [srijan55@gmail.com](mailto:srijan55@gmail.com) wrote:

> We have run into this weird problem in our cluster deployment where at  
> random  
> nodes don't recieve the latest cluster state, and when this happens, they  
> just lie there without actually doing anything with the cluster, this fails  
> the scenarios where we are either indexing or searching from the shards on  
> the node. The cluster (other nodes or master) still report the state is  
> healthy, but the only mitigation to let the things moving on the node,  
> which  
> we have found is to recycle the Elasticsearch service on the node.  
> So far there has been no co-relation between any activity and this problem,  
> any hints would be helpful.
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/Nodes-randomly-not-getting-latest-cluster-state-tp4063966.html](http://elasticsearch-users.115913.n3.nabble.com/Nodes-randomly-not-getting-latest-cluster-state-tp4063966.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/1411567793551-4063966.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1411567793551-4063966.post%40n3.nabble.com)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624byvKOqe33R1U8PH%3DSo-EJRnCkHgFv2ChzdTWg64LoyWQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624byvKOqe33R1U8PH%3DSo-EJRnCkHgFv2ChzdTWg64LoyWQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![srijan55](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@srijan55](https://discuss.elastic.co/u/srijan55)
#### Post date: [September 26, 2014, 6:07pm UTC](https://discuss.elastic.co/t/nodes-randomly-not-getting-latest-cluster-state/19945/3 "2014-09-26T18:07:17Z")

</div>

Most of the times the logs around the problem are related to try to index a document which doesn't conform to the mappings (We expect this can happen some time). We are running a big cluster with 50 data nodes and 3 masters. Data is about a TB. Indexes are 5 indexes per day, with approximately 100k documents in the biggest indexes.

---

<div class="post-metadata">

### Author: ![srijan55](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@srijan55](https://discuss.elastic.co/u/srijan55)
#### Post date: [September 26, 2014, 9:22pm UTC](https://discuss.elastic.co/t/nodes-randomly-not-getting-latest-cluster-state/19945/4 "2014-09-26T21:22:48Z")

</div>

Forgot to mention ES - 1.3.2 Java-7

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:59am UTC](https://discuss.elastic.co/t/nodes-randomly-not-getting-latest-cluster-state/19945/5 "2017-07-06T00:59:39Z")

</div>


