# Transport\_address not matching unicast host values **URL:** \ **Category:** Elasticsearch\ **Created:** [August 15, 2013, 4:15pm UTC](https://discuss.elastic.co/t/transport-address-not-matching-unicast-host-values/13227 "2013-08-15T16:15:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Joseph\_Hammerman](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@Joseph\_Hammerman](https://discuss.elastic.co/u/Joseph_Hammerman)\ **Post date:** [August 15, 2013, 4:15pm UTC](https://discuss.elastic.co/t/transport-address-not-matching-unicast-host-values/13227/1 "2013-08-15T16:15:32Z")
Hi Elastic Search users, We are seeing a rather strange issue. I have reviewed the email archives and I do not see this issue addressed already. We have discovery.zen.ping.multicast.enabled: false in our elasticsearch.yml. The cluster comes up and the state is green, and the nodes are aware of each other. The strangeness is that the transport\_address value returned in the cluster state query does not match the values in discovery.zen.ping.unicast.hosts - it is using a different interface on the machines. Does anyone have any insight? Would be happy to pastebin all of these results. Thanks, Joe -- 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:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [August 17, 2013, 2:43pm UTC](https://discuss.elastic.co/t/transport-address-not-matching-unicast-host-values/13227/2 "2013-08-17T14:43:43Z")
Values in discovery.zen.ping.unicast.hosts are used only for initial discovery. In other words they are used by a node to find other nodes in the cluster. An interface that a particular node is binding to or publishing for other nodes to use doesn't depend on discovery.zen.ping.unicast.hosts but instead it is controlled by network.host, network.bind\_host and network.publish\_host settings. See [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/network/) for more information. On Thursday, August 15, 2013 12:15:32 PM UTC-4, Joseph Hammerman wrote: > Hi Elastic Search users, > > We are seeing a rather strange issue. I have reviewed the email archives > and I do not see this issue addressed already. We > have discovery.zen.ping.multicast.enabled: false in our elasticsearch.yml. > The cluster comes up and the state is green, and the nodes are aware of > each other. > > The strangeness is that the transport\_address value returned in the > cluster state query does not match the values in > discovery.zen.ping.unicast.hosts - it is using a different interface on the > machines. > > Does anyone have any insight? Would be happy to pastebin all of these > results. > > Thanks, > Joe -- 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:20am UTC](https://discuss.elastic.co/t/transport-address-not-matching-unicast-host-values/13227/3 "2017-07-06T02:20:46Z")
Closed on July 6, 2017, 2:20am UTC