# Percolator requests return inconsistent/empty results **URL:** \ **Category:** Elasticsearch\ **Created:** [May 17, 2013, 2:51am UTC](https://discuss.elastic.co/t/percolator-requests-return-inconsistent-empty-results/12003 "2013-05-17T02:51:55Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Oli\_McCormack](https://avatars.discourse-cdn.com/v4/letter/o/fbc32d/32.png) [@Oli\_McCormack](https://discuss.elastic.co/u/Oli_McCormack)\ **Post date:** [May 17, 2013, 2:51am UTC](https://discuss.elastic.co/t/percolator-requests-return-inconsistent-empty-results/12003/1 "2013-05-17T02:51:55Z")
Hi, We're experience an issue where calls to \_percolate return inconsistent results based on which node we hit. Unfortunately I don't have a reproducible case, this seems to occur intermittently but I can't diagnose why. Anyone who has experienced this/can suggest debug steps is appreciated. Here's an example of what we see: ~$ curl -XGET 'node1.endpoint:9200/abc/def/\_percolate' -d '{"doc":{"foo":"bar"}}' {"ok":true,"matches":["some-result"]} ~$ curl -XGET 'node2.endpoint:9200/abc/def/\_percolate' -d '{"doc":{"foo":"bar"}}' {"ok":true,"matches":[]} Furthermore, we'll see for the "docs" entry in the below calls: ~$ curl -XGET endpoint.node1:9200/\_percolator/\_status "docs" : { "num\_docs" : 8, "max\_doc" : 8, "deleted\_docs" : 0 } ~$ curl -XGET endpoint.node2:9200/\_percolator/\_status "docs" : { "num\_docs" : 8, "max\_doc" : 11, "deleted\_docs" : 3 } Some notes on the occurrence: - We're running 5 nodes, and we will see "matches": [] across some number of them (2 during the most recent event). - The results returned from each node are consistent, meaning that we will receive empty matches repeatedly from the same bad node. - Flushing or refreshing do not resolve this. Resolution: The only way we can resolve this at the moment is by deleting the \_percolator index and re-submitting entries to it. I'm happy to dig into this further if anyone has alternative debugging steps, otherwise I'll likely file a bug. This is running on Ubuntu with java version 1.6.0\_27. We have 5 nodes, 3 indices. ES: 0.20.4 with s3 as the gateway.type. Thanks oli -- 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:** ![Oli\_McCormack](https://avatars.discourse-cdn.com/v4/letter/o/fbc32d/32.png) [@Oli\_McCormack](https://discuss.elastic.co/u/Oli_McCormack)\ **Post date:** [May 30, 2013, 6:45pm UTC](https://discuss.elastic.co/t/percolator-requests-return-inconsistent-empty-results/12003/2 "2013-05-30T18:45:14Z")
I've filed a bug for this: [Percolator requests return inconsistent/empty results · Issue #3121 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/3121) I believe it's a duplicate of: [Percolator responses become inconsistent with cluster after forceful reboot of a node · Issue #2531 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2531) which has been alive for a while but is unresolved. As an aside, I also noticed that the files on disk on each of the machines machines: /location/elasticsearch/nodes/0/indices/\_percolator/0/index/\_0.fdt had the same content. I added this information to the ticket. - oli On Thursday, May 16, 2013 7:51:55 PM UTC-7, Oli wrote: > Hi, > > We're experience an issue where calls to \_percolate return inconsistent > results based on which node we hit. Unfortunately I don't have > a reproducible case, this seems to occur intermittently but I can't > diagnose why. Anyone who has experienced this/can suggest debug steps is > appreciated. > > Here's an example of what we see: > ~$ curl -XGET 'node1.endpoint:9200/abc/def/\_percolate' -d > '{"doc":{"foo":"bar"}}' > {"ok":true,"matches":["some-result"]} > ~$ curl -XGET 'node2.endpoint:9200/abc/def/\_percolate' -d > '{"doc":{"foo":"bar"}}' > {"ok":true,"matches":} > > Furthermore, we'll see for the "docs" entry in the below calls: > ~$ curl -XGET endpoint.node1:9200/\_percolator/\_status > "docs" : { "num\_docs" : 8, "max\_doc" : 8, "deleted\_docs" : 0 } > ~$ curl -XGET endpoint.node2:9200/\_percolator/\_status > "docs" : { "num\_docs" : 8, "max\_doc" : 11, "deleted\_docs" : 3 } > > Some notes on the occurrence: > > - We're running 5 nodes, and we will see "matches": across some number > of them (2 during the most recent event). > - The results returned from each node are consistent, meaning that we will > receive empty matches repeatedly from the same bad node. > - Flushing or refreshing do not resolve this. > > Resolution: > The only way we can resolve this at the moment is by deleting the > \_percolator index and re-submitting entries to it. > > I'm happy to dig into this further if anyone has alternative debugging > steps, otherwise I'll likely file a bug. > > This is running on Ubuntu with java version 1.6.0\_27. We have 5 nodes, 3 > indices. ES: 0.20.4 with s3 as the gateway.type. > > Thanks > oli -- 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:33am UTC](https://discuss.elastic.co/t/percolator-requests-return-inconsistent-empty-results/12003/3 "2017-07-06T02:33:48Z")