# Elasticsearch Cluster - Non-Master Node Doesn't Join the Intended Cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [January 31, 2014, 11:39pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-non-master-node-doesnt-join-the-intended-cluster/15542 "2014-01-31T23:39:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Indra\_Suryanata](https://avatars.discourse-cdn.com/v4/letter/i/eb9ed0/32.png) [@Indra\_Suryanata](https://discuss.elastic.co/u/Indra_Suryanata)\ **Post date:** [January 31, 2014, 11:39pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-non-master-node-doesnt-join-the-intended-cluster/15542/1 "2014-01-31T23:39:18Z")
I am a beginner on Elasticsearch. I have Logstash/Elasticsearch/Kibana running in HP Cloud. This is the master node. I tried to have at least another node (also in HP Cloud) to set up an Elasticsearch cluster. However, I found the non-master node still doesn’t join the intended cluster. My setup is the following: Master Node elasticsearch 0.90.3 logstash 1.2.2 kibana 3.0.0milestone4 In /etc/elasticsearch/elasticsearch.yml: cluster.name: ls\_cluster node.name: logstash1 Non-Master Node elasticsearch 0.90.3 logstash 1.2.2 kibana 3.0.0milestone4 In /etc/elasticsearch/elasticsearch.yml: cluster.name: ls\_cluster node.name: logstash2 I also tried changing the following on the non-master node, but it didn’t make any difference. node.master: false node.data: true transport.tcp.port: 9301 http.port: 9201 The same result with using elasticsearch 0.90.9 & logstash 1.3.3. Any help is appreciated, thanks! -- 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/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [January 31, 2014, 11:41pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-non-master-node-doesnt-join-the-intended-cluster/15542/2 "2014-01-31T23:41:02Z")
What is your zen discovery method? > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 1 February 2014 10:39, Indra Suryanata [insury@gmail.com](mailto:insury@gmail.com) wrote: > I am a beginner on Elasticsearch. > I have Logstash/Elasticsearch/Kibana running in HP Cloud. > This is the master node. > > I tried to have at least another node (also in HP Cloud) to set up an > Elasticsearch cluster. > However, I found the non-master node still doesn't join the intended > cluster. > > My setup is the following: > Master Node > elasticsearch 0.90.3 > logstash 1.2.2 > kibana 3.0.0milestone4 > In /etc/elasticsearch/elasticsearch.yml: > cluster.name: ls\_cluster > node.name: logstash1 > > Non-Master Node > elasticsearch 0.90.3 > logstash 1.2.2 > kibana 3.0.0milestone4 > In /etc/elasticsearch/elasticsearch.yml: > cluster.name: ls\_cluster > node.name: logstash2 > > I also tried changing the following on the non-master node, but it didn't > make any difference. > node.master: false > node.data: true > transport.tcp.port: 9301 > http.port: 9201 > > The same result with using elasticsearch 0.90.9 & logstash 1.3.3. > > Any help is appreciated, thanks! > > -- > 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/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae%40googlegroups.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/CAEM624ZbVR0YqFZbEfvyUV5P6SL%2BD8sMhSZWKNRnZxffuhXMag%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZbVR0YqFZbEfvyUV5P6SL%2BD8sMhSZWKNRnZxffuhXMag%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Indra\_Suryanata](https://avatars.discourse-cdn.com/v4/letter/i/eb9ed0/32.png) [@Indra\_Suryanata](https://discuss.elastic.co/u/Indra_Suryanata)\ **Post date:** [February 1, 2014, 12:00am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-non-master-node-doesnt-join-the-intended-cluster/15542/3 "2014-02-01T00:00:41Z")
Hi Mark, I didn't set anything in the zen discovery method. Should I set it to network.host: discovery.zen.ping.unicast.hosts: in both elasticsearch.yml of the Master Node & Non-Master Node? Thanks! Regards, Indra On Friday, January 31, 2014 3:41:02 PM UTC-8, Mark Walkom wrote: > What is your zen discovery method? > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html) > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 1 February 2014 10:39, Indra Suryanata \<[ins...@gmail.com](mailto:ins...@gmail.com) \\>wrote: > > > I am a beginner on Elasticsearch. > > I have Logstash/Elasticsearch/Kibana running in HP Cloud. > > This is the master node. > > > > I tried to have at least another node (also in HP Cloud) to set up an > > Elasticsearch cluster. > > However, I found the non-master node still doesn’t join the intended > > cluster. > > > > My setup is the following: > > Master Node > > elasticsearch 0.90.3 > > logstash 1.2.2 > > kibana 3.0.0milestone4 > > In /etc/elasticsearch/elasticsearch.yml: > > cluster.name: ls\_cluster > > node.name: logstash1 > > > > Non-Master Node > > elasticsearch 0.90.3 > > logstash 1.2.2 > > kibana 3.0.0milestone4 > > In /etc/elasticsearch/elasticsearch.yml: > > cluster.name: ls\_cluster > > node.name: logstash2 > > > > I also tried changing the following on the non-master node, but it didn’t > > make any difference. > > node.master: false > > node.data: true > > transport.tcp.port: 9301 > > http.port: 9201 > > > > The same result with using elasticsearch 0.90.9 & logstash 1.3.3. > > > > Any help is appreciated, thanks! > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae%40googlegroups.com) > > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/ccf83335-cc8e-4cef-b602-ffaf4f683c58%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ccf83335-cc8e-4cef-b602-ffaf4f683c58%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [February 1, 2014, 12:08am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-non-master-node-doesnt-join-the-intended-cluster/15542/4 "2014-02-01T00:08:19Z")
network.host is the IP that the node itself will listen on when advertising the service, so if you set that to the master node IP then each node will try and listen on that same IP. Which is not what you want. You want to set; discovery.zen.ping.unicast: $IP\_OF\_MASTER Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 1 February 2014 11:00, Indra Suryanata [insury@gmail.com](mailto:insury@gmail.com) wrote: > Hi Mark, > > I didn't set anything in the zen discovery method. > Should I set it to > > network.host: > > discovery.zen.ping.unicast.hosts: > > in both elasticsearch.yml of the Master Node & Non-Master Node? > > Thanks! > > Regards, > Indra > > On Friday, January 31, 2014 3:41:02 PM UTC-8, Mark Walkom wrote: > > > What is your zen discovery method? [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/) > > elasticsearch/reference/current/modules-discovery-zen.html > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 1 February 2014 10:39, Indra Suryanata [ins...@gmail.com](mailto:ins...@gmail.com) wrote: > > > > > I am a beginner on Elasticsearch. > > > I have Logstash/Elasticsearch/Kibana running in HP Cloud. > > > This is the master node. > > > > > > I tried to have at least another node (also in HP Cloud) to set up an > > > Elasticsearch cluster. > > > However, I found the non-master node still doesn't join the intended > > > cluster. > > > > > > My setup is the following: > > > Master Node > > > elasticsearch 0.90.3 > > > logstash 1.2.2 > > > kibana 3.0.0milestone4 > > > In /etc/elasticsearch/elasticsearch.yml: > > > cluster.name: ls\_cluster > > > node.name: logstash1 > > > > > > Non-Master Node > > > elasticsearch 0.90.3 > > > logstash 1.2.2 > > > kibana 3.0.0milestone4 > > > In /etc/elasticsearch/elasticsearch.yml: > > > cluster.name: ls\_cluster > > > node.name: logstash2 > > > > > > I also tried changing the following on the non-master node, but it > > > didn't make any difference. > > > node.master: false > > > node.data: true > > > transport.tcp.port: 9301 > > > http.port: 9201 > > > > > > The same result with using elasticsearch 0.90.9 & logstash 1.3.3. > > > > > > Any help is appreciated, thanks! > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae% > > > [40googlegroups.com](http://40googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > 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/ccf83335-cc8e-4cef-b602-ffaf4f683c58%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ccf83335-cc8e-4cef-b602-ffaf4f683c58%40googlegroups.com) > > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/CAEM624bqqWVp0vJKJ%2BVMiG5eOgR7dcuEOBgwrr3HOfS9CTjW3Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bqqWVp0vJKJ%2BVMiG5eOgR7dcuEOBgwrr3HOfS9CTjW3Q%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Indra\_Suryanata](https://avatars.discourse-cdn.com/v4/letter/i/eb9ed0/32.png) [@Indra\_Suryanata](https://discuss.elastic.co/u/Indra_Suryanata)\ **Post date:** [February 3, 2014, 10:35am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-non-master-node-doesnt-join-the-intended-cluster/15542/5 "2014-02-03T10:35:42Z")
Thanks Mark, it works! - Really appreciate your help. As you suggested, I set discovery.zen.ping.unicast.hosts: $IP\_OF\_MASTER in elasticsearch.yml of the Non-Master Node. Regards, Indra On Friday, January 31, 2014 4:08:19 PM UTC-8, Mark Walkom wrote: > network.host is the IP that the node itself will listen on when > advertising the service, so if you set that to the master node IP then each > node will try and listen on that same IP. Which is not what you want. > > You want to set; > discovery.zen.ping.unicast: $IP\_OF\_MASTER > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 1 February 2014 11:00, Indra Suryanata \<[ins...@gmail.com](mailto:ins...@gmail.com) \\>wrote: > > > Hi Mark, > > > > I didn't set anything in the zen discovery method. > > Should I set it to > > > > network.host: > > > > discovery.zen.ping.unicast.hosts: > > > > in both elasticsearch.yml of the Master Node & Non-Master Node? > > > > Thanks! > > > > Regards, > > Indra > > > > On Friday, January 31, 2014 3:41:02 PM UTC-8, Mark Walkom wrote: > > > > > What is your zen discovery method? [http://www](http://www). > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/) > > > current/modules-discovery-zen.html > > > > > > Regards, > > > Mark Walkom > > > > > > Infrastructure Engineer > > > Campaign Monitor > > > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) > > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > > > On 1 February 2014 10:39, Indra Suryanata [ins...@gmail.com](mailto:ins...@gmail.com) wrote: > > > > > > > I am a beginner on Elasticsearch. > > > > I have Logstash/Elasticsearch/Kibana running in HP Cloud. > > > > This is the master node. > > > > > > > > I tried to have at least another node (also in HP Cloud) to set up an > > > > Elasticsearch cluster. > > > > However, I found the non-master node still doesn’t join the intended > > > > cluster. > > > > > > > > My setup is the following: > > > > Master Node > > > > elasticsearch 0.90.3 > > > > logstash 1.2.2 > > > > kibana 3.0.0milestone4 > > > > In /etc/elasticsearch/elasticsearch.yml: > > > > cluster.name: ls\_cluster > > > > node.name: logstash1 > > > > > > > > Non-Master Node > > > > elasticsearch 0.90.3 > > > > logstash 1.2.2 > > > > kibana 3.0.0milestone4 > > > > In /etc/elasticsearch/elasticsearch.yml: > > > > cluster.name: ls\_cluster > > > > node.name: logstash2 > > > > > > > > I also tried changing the following on the non-master node, but it > > > > didn’t make any difference. > > > > node.master: false > > > > node.data: true > > > > transport.tcp.port: 9301 > > > > http.port: 9201 > > > > > > > > The same result with using elasticsearch 0.90.9 & logstash 1.3.3. > > > > > > > > Any help is appreciated, thanks! > > > > > > > > -- > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/be40c6b9-4fe5-45ca-b19f-69eadb00a1ae% > > > > [40googlegroups.com](http://40googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/ccf83335-cc8e-4cef-b602-ffaf4f683c58%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ccf83335-cc8e-4cef-b602-ffaf4f683c58%40googlegroups.com) > > > . > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/4349d68a-72a5-49fa-ace5-2bc8ddc79e60%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4349d68a-72a5-49fa-ace5-2bc8ddc79e60%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 1:53am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-non-master-node-doesnt-join-the-intended-cluster/15542/6 "2017-07-06T01:53:11Z")