# Elasticsearch cluster is not working properly

**URL:** <https://discuss.elastic.co/t/elasticsearch-cluster-is-not-working-properly/52259>\
**Category:** Elasticsearch\
**Created:** [June 8, 2016, 9:53pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-is-not-working-properly/52259 "2016-06-08T21:53:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Praveenj](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@Praveenj](https://discuss.elastic.co/u/Praveenj)\
**Post date:** [June 8, 2016, 9:53pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-is-not-working-properly/52259/1 "2016-06-08T21:53:12Z")

</div>

We are using clustered elasticsearch setup in our environment. We have a 4 nodes in a cluster. But, sometimes, every nodes acts as a separate cluster. Whenever i tried to run [elasticsearchnode]/\_cat/nodes?v. Everytime gives different node name as output. After that, we restarted the elasticsearch services. Now, it seems to be joined into the cluster but elasticsearch logs, we are seeing "Caused by: org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution (queue capacity 100) on org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler@7db74275". Tried with setting threadpool configuration and unicast configuration. Did not works still.

Elasticsearch version: 1.3.3

---

<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:** [June 8, 2016, 9:58pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-is-not-working-properly/52259/2 "2016-06-08T21:58:44Z")

</div>

> [@Praveenj](#):
>
> Elasticsearch version: 1.3.3

Upgrade ASAP, this is a _very_ outdated version.

What do your settings on each node look like?

---

<div class="post-metadata">

**Author:** ![Praveenj](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@Praveenj](https://discuss.elastic.co/u/Praveenj)\
**Post date:** [June 9, 2016, 5:06pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-is-not-working-properly/52259/3 "2016-06-09T17:06:01Z")

</div>

Please find elasticsearch.yml configuration file,

### MANAGED BY PUPPET

* * *

bootstrap:  
mlockall: true  
cloud:  
aws:  
region: us-east-1  
cluster:  
name:   
discovery:  
ec2:  
tag:  
aws:cloudformation:logical-id: loggingsearchmanagerAutoScalingGroup  
type: ec2  
index:  
number\_of\_replicas: 1  
number\_of\_shards: 20  
logging\_defaults:  
action: ERROR  
path:  
data: /mnt/elasticsearch  
logs: /var/log/elasticsearch  
repositories:  
s3:  
base\_path: /backups/elasticsearch/  
bucket:   
chunk\_size: 100m  
compress: true  
concurrent\_streams: 10

---

<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:** [June 9, 2016, 9:36pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-is-not-working-properly/52259/4 "2016-06-09T21:36:06Z")

</div>

You need to upgrade, urgently.  
Then read this chapter of the Definitive Guide - [https://www.elastic.co/guide/en/elasticsearch/guide/current/deploy.html](https://www.elastic.co/guide/en/elasticsearch/guide/current/deploy.html)

---

<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 5, 2017, 10:44pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-is-not-working-properly/52259/5 "2017-07-05T22:44:55Z")

</div>