# Inconsistent query result due to communication failure between nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [June 26, 2013, 10:04am UTC](https://discuss.elastic.co/t/inconsistent-query-result-due-to-communication-failure-between-nodes/12549 "2013-06-26T10:04:19Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Ankit\_Jain](https://avatars.discourse-cdn.com/v4/letter/a/96bed5/32.png) [@Ankit\_Jain](https://discuss.elastic.co/u/Ankit_Jain)\ **Post date:** [June 26, 2013, 10:04am UTC](https://discuss.elastic.co/t/inconsistent-query-result-due-to-communication-failure-between-nodes/12549/1 "2013-06-26T10:04:19Z")
Hi All, We are using transport client to connect to ES. While querying on ES, we are getting inconsistent results: We are using cluster of two nodes. For example: When we are firing query first time, the number of hits is 50 while executing the same query second time returns 100 hits. This is happening because the transport client execute the request in round robin. So, first query goes to NodeA while other one goes to NodeB. The results are coming inconsistent because nodes are not able to communicate with each other. I would like to know the reasons of connection lost / communication failure between the nodes. Thanks, Ankit Jain iLabs -- 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:** [June 26, 2013, 10:13am UTC](https://discuss.elastic.co/t/inconsistent-query-result-due-to-communication-failure-between-nodes/12549/2 "2013-06-26T10:13:38Z")
What I've seen in the past about this is: Network failure between both nodes Out of memory exception So shards are not synchronized anymore. Basically it ends up to raise split brain issue. It might happen when using only 2 nodes. If you know that NodeA have the right number of docs, stop NodeB, remove in /data dir the `bad` index. Restart NodeB. It will recover docs from NodeA. My 2 cents -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 26 juin 2013 à 12:04, Ankit Jain [ankitjaincs06@gmail.com](mailto:ankitjaincs06@gmail.com) a écrit : > Hi All, > > We are using transport client to connect to ES. While querying on ES, we are getting inconsistent results: > > We are using cluster of two nodes. > > For example: > When we are firing query first time, the number of hits is 50 while executing the same query second time returns 100 hits. This is happening because the transport client execute the request in round robin. So, first query goes to NodeA while other one goes to NodeB. > > The results are coming inconsistent because nodes are not able to communicate with each other. > > I would like to know the reasons of connection lost / communication failure between the nodes. > > Thanks, > Ankit Jain > iLabs > > -- > 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:** ![Ankit\_Jain](https://avatars.discourse-cdn.com/v4/letter/a/96bed5/32.png) [@Ankit\_Jain](https://discuss.elastic.co/u/Ankit_Jain)\ **Post date:** [June 26, 2013, 10:33am UTC](https://discuss.elastic.co/t/inconsistent-query-result-due-to-communication-failure-between-nodes/12549/3 "2013-06-26T10:33:04Z")
Hi David, Thanks for the reply. ~Ankit On Wednesday, 26 June 2013 10:13:38 UTC, David Pilato wrote: > What I've seen in the past about this is: > Network failure between both nodes > Out of memory exception > > So shards are not synchronized anymore. > > Basically it ends up to raise split brain issue. It might happen when > using only 2 nodes. > > If you know that NodeA have the right number of docs, stop NodeB, remove > in /data dir the `bad` index. Restart NodeB. > It will recover docs from NodeA. > > My 2 cents > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 26 juin 2013 à 12:04, Ankit Jain \<[ankitj...@gmail.com](mailto:ankitj...@gmail.com) \\> a > écrit : > > Hi All, > > We are using transport client to connect to ES. While querying on ES, we > are getting inconsistent results: > > We are using cluster of two nodes. > > For example: > When we are firing query first time, the number of hits is 50 while > executing the same query second time returns 100 hits. This is happening > because the transport client execute the request in round robin. So, first > query goes to NodeA while other one goes to NodeB. > > The results are coming inconsistent because nodes are not able to > communicate with each other. > > I would like to know the reasons of connection lost / communication > failure between the nodes. > > Thanks, > Ankit Jain > iLabs > > -- > 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) \. > 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:** ![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:29am UTC](https://discuss.elastic.co/t/inconsistent-query-result-due-to-communication-failure-between-nodes/12549/4 "2017-07-06T02:29:24Z")
Closed on July 6, 2017, 2:29am UTC