# Elasticsearch Cluster setup Issue

**URL:** <https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561>\
**Category:** Elasticsearch\
**Created:** [September 18, 2015, 11:06am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561 "2015-09-18T11:06:20Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [September 18, 2015, 11:06am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/1 "2015-09-18T11:06:20Z")

</div>

Hi,  
I tried to setup Elasticsearch cluster in my local LAB.

**Setup Scenario :**

**Server 1 :**  
IP : 10.11.12.101  
Cluster Name : mycluster  
Node name : Node\_2

**Server 2 :**  
IP : 10.11.12.102  
Cluster Name : mycluster  
Node name : Node\_1

Inserted some document in Server 1. But it doesn't replicated in Server 2. Rather than , it shows "Unassigned" option when view the Elasticsearch using head plugin [[http://10.11.12.101:9200/\_plugin/head](http://10.11.12.101:9200/_plugin/head) ].

![](https://us1.discourse-cdn.com/elastic/original/2X/5/518c4b888d6292f68ab9c6441eccc0cfe7ef5c47.png)

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 18, 2015, 11:27am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/2 "2015-09-18T11:27:17Z")

</div>

Nodes are not seeing each other.

What is your version?  
What can you see in logs?  
Check the network connections.  
What is your elasticsearch.yml?

---

<div class="post-metadata">

**Author:** ![pandiyancool](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pandiyancool/32/3431_2.png) [@pandiyancool](https://discuss.elastic.co/u/pandiyancool)\
**Post date:** [September 18, 2015, 1:20pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/3 "2015-09-18T13:20:11Z")

</div>

I guess your nodes are not able to ping with each other. Check the firewall settings or simply add Inbound rules & Outbound rules for ports 9200 & 9300 respectively on nodes. 🙂

---

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [September 18, 2015, 2:20pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/4 "2015-09-18T14:20:35Z")

</div>

@pandiyancool ,, , No , Your guess is wrong 😄 .

The problem is fixed, its due to multicast option was set to False on one of the node configuration file.

---

<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 19, 2015, 12:59am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/5 "2015-09-19T00:59:29Z")

</div>

We do recommend the use of unicast, ES 2.0 will move multicast to a plugin and we will default to unicast instead.

---

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [September 19, 2015, 5:51am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/6 "2015-09-19T05:51:12Z")

</div>

oh okay. I will change settings. will get back to u incase of any issues

Mark Walkom [noreply@discuss.elastic.co](mailto:noreply@discuss.elastic.co) wrote:

---

<div class="post-metadata">

**Author:** ![pandiyancool](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pandiyancool/32/3431_2.png) [@pandiyancool](https://discuss.elastic.co/u/pandiyancool)\
**Post date:** [September 20, 2015, 7:37am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/7 "2015-09-20T07:37:49Z")

</div>

OK great !!!

---

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [September 22, 2015, 8:02am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/8 "2015-09-22T08:02:23Z")

</div>

@warkolm , As per your suggestion , I have changed my settings to unicast. But still have some confusion on data update.

![](https://us1.discourse-cdn.com/elastic/original/2X/3/3c4e04512109e85a99ccddd6df855d3e37dc6dec.png)

Now, both cluster nodes are shown when check it over head plugin. Then I tried to post some data into in one of the nodes [ex, updated in Node\_2 cluster]. I could see the same data on Node\_3 cluster.

but, when I check the cluster status through head plugin, it shows cluster health in Yellow color. Can you please give some explanation from the above screenshot ? . When cluster health is in Yellow state and why still Unassigned is there ?

Shared : 5  
replica : 1

---

<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 22, 2015, 9:31am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/9 "2015-09-22T09:31:31Z")

</div>

Yellow means you have unassigned replicas.  
Why? You should check your logs to see if there is something keeping them from being allocated.

---

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [September 22, 2015, 9:57am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/10 "2015-09-22T09:57:41Z")

</div>

Yeah, I checked my logs already. But couldn't find anything suspicious.

Here is the log  
[2015-09-21 08:51:14,662][INFO][node] [Node\_2] initialized  
[2015-09-21 08:51:14,662][INFO][node] [Node\_2] starting ...  
[2015-09-21 08:51:14,776][INFO][transport] [Node\_2] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/x.x.x.x:9300]}  
[2015-09-21 08:51:14,786][INFO][discovery] [Node\_2] mycluster/v10zYWrHSGSX9nyXLeNg8w  
[2015-09-21 08:51:17,803][INFO][cluster.service] [Node\_2] new\_master [Node\_2][v10zYWrHSGSX9nyXLeNg8w][[logstash.example.com](http://logstash.example.com)][inet[/x.x.x.x:9300]], reason: zen-disco-join (elected\_as\_master)  
[2015-09-21 08:51:17,842][INFO][http] [Node\_2] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/180.87.10.125:9200]}  
[2015-09-21 08:51:17,843][INFO][node] [Node\_2] started  
[2015-09-21 08:51:17,869][INFO][gateway] [Node\_2] recovered [0] indices into cluster\_state  
[2015-09-21 08:51:22,476][INFO][cluster.service] [Node\_2] added {[Node\_3][MD1MbBxmQNesAt0sFA5wig][localhost][inet[/x.x.x.x:9300]],}, reason: zen-disco-receive(join from node[[Node\_3][MD1MbBxmQNesAt0sFA5wig][localhost][inet[/x.x.x.x:9300]]])  
[2015-09-21 08:51:35,169][INFO][cluster.metadata] [Node\_2] [mybucket] creating index, cause [api], shards [5]/[1], mappings [doc]

One more question, Why Node\_2 shows only 1 and 3. Remaining [0,2,4] are shown as Unassigned. Please give some more detail about that.

---

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [September 22, 2015, 2:43pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/11 "2015-09-22T14:43:34Z")

</div>

Any idea ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 22, 2015, 3:08pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/12 "2015-09-22T15:08:18Z")

</div>

Are the nodes running the same version of Elasticsearch?

---

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [September 22, 2015, 3:10pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/13 "2015-09-22T15:10:54Z")

</div>

No. Each node is running on separate versions

Node 1 version: 1.3.7  
Node 2 version : 1.5.2

I don't think that version compatibility is the problem here. Could you please confirm it ?.

---

<div class="post-metadata">

**Author:** ![colings86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/colings86/32/44960_2.png) [@colings86](https://discuss.elastic.co/u/colings86)\
**Post date:** [September 22, 2015, 3:22pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/14 "2015-09-22T15:22:41Z")

</div>

Mixed version clusters are not supported for long term use. You should only have a mixed version cluster while upgrading, but you should strive to upgrade all node to the same version as soon as possible.

Elasticsearch will not assign replicas to a node which is on an older version than the node holding the primary shard(s). This is why your replicas are unassigned, you need to upgrade node 1 to be on the same version as node 2.

---

<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, 11:48pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-setup-issue/29561/15 "2017-07-05T23:48:47Z")

</div>


