# Wrong routing of TransportClient with sniffing enabled **URL:** \ **Category:** Elasticsearch\ **Created:** [December 19, 2014, 7:09am UTC](https://discuss.elastic.co/t/wrong-routing-of-transportclient-with-sniffing-enabled/21324 "2014-12-19T07:09:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jae/32/791_2.png) [@Jae](https://discuss.elastic.co/u/Jae)\ **Post date:** [December 19, 2014, 7:09am UTC](https://discuss.elastic.co/t/wrong-routing-of-transportclient-with-sniffing-enabled/21324/1 "2014-12-19T07:09:44Z")
Hi I am using ES 1.1.0 with TransportClient. We observed wrong routing from TransportClient when we scale up the cluster. For example, suppose that we have two ES clusters, es0, es1 and es\_sink\_0 is the TransportClient talking to es0, es\_sink\_1 is one talking to es1. If we scale up es1, it happens that es\_sink\_0 is sending data to es1. We are using client.transport.sniff=true by default. This should not happen theoretically because TransportClient will refresh its server list through communicating with the cluster and new nodes should not join to the wrong cluster. Is there anybody who has seen this problem before? Any comments will be totally appreciated. We didn't find the root cause yet but this is the really serious problem. So, temporarily, I want to turn off sniff and add the feature that manually updates the server list through external discover module. -- 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/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [December 19, 2014, 9:56am UTC](https://discuss.elastic.co/t/wrong-routing-of-transportclient-with-sniffing-enabled/21324/2 "2014-12-19T09:56:31Z")
You must set client.transport.ignore\_cluster\_name to "false", see > **[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. Jörg On Fri, Dec 19, 2014 at 8:09 AM, Jae [metacret@gmail.com](mailto:metacret@gmail.com) wrote: > Hi > > I am using ES 1.1.0 with TransportClient. > > We observed wrong routing from TransportClient when we scale up the > cluster. For example, suppose that we have two ES clusters, es0, es1 and > es\_sink\_0 is the TransportClient talking to es0, es\_sink\_1 is one talking > to es1. If we scale up es1, it happens that es\_sink\_0 is sending data to > es1. We are using client.transport.sniff=true by default. This should not > happen theoretically because TransportClient will refresh its server list > through communicating with the cluster and new nodes should not join to the > wrong cluster. > > Is there anybody who has seen this problem before? Any comments will be > totally appreciated. We didn't find the root cause yet but this is the > really serious problem. So, temporarily, I want to turn off sniff and add > the feature that manually updates the server list through external discover > module. > > -- > 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/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAKdsXoH2eMmpbvo%2Bvymyg6Y5XxxYTd\_dABZ2VkmNJfa-bVKXNA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eMmpbvo%2Bvymyg6Y5XxxYTd_dABZ2VkmNJfa-bVKXNA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jae/32/791_2.png) [@Jae](https://discuss.elastic.co/u/Jae)\ **Post date:** [December 19, 2014, 5:58pm UTC](https://discuss.elastic.co/t/wrong-routing-of-transportclient-with-sniffing-enabled/21324/3 "2014-12-19T17:58:03Z")
I already did because it's default right? Also, I am seeing the following which is the proof of not ignoring cluster name. 2014-12-19 06:58:08,187 WARN elasticsearch[Sun Girl][generic][T#49358] transport - [Sun Girl] node null not part of the cluster Cluster [es\_logsummary], ignoring... On Fri, Dec 19, 2014 at 1:56 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > You must set > > client.transport.ignore\_cluster\_name > > to "false", see > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html) > > Jörg > > On Fri, Dec 19, 2014 at 8:09 AM, Jae [metacret@gmail.com](mailto:metacret@gmail.com) wrote: > > > Hi > > > > I am using ES 1.1.0 with TransportClient. > > > > We observed wrong routing from TransportClient when we scale up the > > cluster. For example, suppose that we have two ES clusters, es0, es1 and > > es\_sink\_0 is the TransportClient talking to es0, es\_sink\_1 is one talking > > to es1. If we scale up es1, it happens that es\_sink\_0 is sending data to > > es1. We are using client.transport.sniff=true by default. This should not > > happen theoretically because TransportClient will refresh its server list > > through communicating with the cluster and new nodes should not join to the > > wrong cluster. > > > > Is there anybody who has seen this problem before? Any comments will be > > totally appreciated. We didn't find the root cause yet but this is the > > really serious problem. So, temporarily, I want to turn off sniff and add > > the feature that manually updates the server list through external discover > > module. > > > > -- > > 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/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7a34e016-b322-48aa-a1de-a43249e7b58d%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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/CAKdsXoH2eMmpbvo%2Bvymyg6Y5XxxYTd\_dABZ2VkmNJfa-bVKXNA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eMmpbvo%2Bvymyg6Y5XxxYTd_dABZ2VkmNJfa-bVKXNA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eMmpbvo%2Bvymyg6Y5XxxYTd\_dABZ2VkmNJfa-bVKXNA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eMmpbvo%2Bvymyg6Y5XxxYTd_dABZ2VkmNJfa-bVKXNA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAKe7ALc%2BCFz9wA4ha\_MK%2BAMMvAv9dJM%2BBPdHExU%2B%3Dq%2BgQoa-cw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKe7ALc%2BCFz9wA4ha_MK%2BAMMvAv9dJM%2BBPdHExU%2B%3Dq%2BgQoa-cw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:42am UTC](https://discuss.elastic.co/t/wrong-routing-of-transportclient-with-sniffing-enabled/21324/4 "2017-07-06T00:42:39Z")