# Master-Slave not detected **URL:** \ **Category:** Elasticsearch\ **Created:** [March 4, 2013, 11:58am UTC](https://discuss.elastic.co/t/master-slave-not-detected/10994 "2013-03-04T11:58:49Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ophir\_Michaeli](https://avatars.discourse-cdn.com/v4/letter/o/9f8e36/32.png) [@Ophir\_Michaeli](https://discuss.elastic.co/u/Ophir_Michaeli)\ **Post date:** [March 4, 2013, 11:58am UTC](https://discuss.elastic.co/t/master-slave-not-detected/10994/1 "2013-03-04T11:58:49Z")
Hi, I have 2 nodes that are on the same cluster and are not recognizing one another (both are becoming "new master" when node loaded). What should I check to resolve the issue? Thanks, Ophir -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [March 4, 2013, 2:04pm UTC](https://discuss.elastic.co/t/master-slave-not-detected/10994/2 "2013-03-04T14:04:58Z")
Did you modify elasticsearch.yml file? Check unicast section if you disabled multicast. Check also your firewall rules and open if needed 9300 port on each node. -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 4 mars 2013 à 12:58, Ophir Michaeli [ophirmichaeli@gmail.com](mailto:ophirmichaeli@gmail.com) a écrit : > Hi, > > I have 2 nodes that are on the same cluster and are not recognizing one another (both are becoming "new master" when node loaded). > What should I check to resolve the issue? > > Thanks, > Ophir > > -- > 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). > 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ophir\_Michaeli](https://avatars.discourse-cdn.com/v4/letter/o/9f8e36/32.png) [@Ophir\_Michaeli](https://discuss.elastic.co/u/Ophir_Michaeli)\ **Post date:** [March 4, 2013, 2:27pm UTC](https://discuss.elastic.co/t/master-slave-not-detected/10994/3 "2013-03-04T14:27:51Z")
Hi, I returned to default yml config and added an inbound rule for port 9300 on both machine nodes, multicast is enabled (by default). The issue remains. Thanks, Ophir On Monday, March 4, 2013 1:58:49 PM UTC+2, Ophir Michaeli wrote: > Hi, > > I have 2 nodes that are on the same cluster and are not recognizing one > another (both are becoming "new master" when node loaded). > > What should I check to resolve the issue? > > Thanks, > > Ophir -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ophir\_Michaeli](https://avatars.discourse-cdn.com/v4/letter/o/9f8e36/32.png) [@Ophir\_Michaeli](https://discuss.elastic.co/u/Ophir_Michaeli)\ **Post date:** [March 14, 2013, 4:21pm UTC](https://discuss.elastic.co/t/master-slave-not-detected/10994/4 "2013-03-14T16:21:54Z")
I used unicast to solve the issue: _Master_ Node elasticsearch.yml file – node.master: true _Slave_ Nodes elasticsearch.yml file – node.master: false discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["46.165.209.139"] (46.165.209.139 is the master's ip address ) On Monday, March 4, 2013 4:27:51 PM UTC+2, Ophir Michaeli wrote: > Hi, > > I returned to default yml config and added an inbound rule for port 9300 > on both machine nodes, multicast is enabled (by default). > > The issue remains. > > Thanks, > > Ophir > > On Monday, March 4, 2013 1:58:49 PM UTC+2, Ophir Michaeli wrote: > > > Hi, > > > > I have 2 nodes that are on the same cluster and are not recognizing one > > another (both are becoming "new master" when node loaded). > > > > What should I check to resolve the issue? > > > > Thanks, > > > > Ophir -- 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). 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, 2:46am UTC](https://discuss.elastic.co/t/master-slave-not-detected/10994/5 "2017-07-06T02:46:25Z")