# Percolate returns empty matches under heavy load during elasticsearch cluster re-sizing

**URL:** <https://discuss.elastic.co/t/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re-sizing/23616>\
**Category:** Elasticsearch\
**Created:** [May 13, 2015, 6:02am UTC](https://discuss.elastic.co/t/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re-sizing/23616 "2015-05-13T06:02:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ekesken](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ekesken/32/44861_2.png) [@ekesken](https://discuss.elastic.co/u/ekesken)\
**Post date:** [May 13, 2015, 6:02am UTC](https://discuss.elastic.co/t/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re-sizing/23616/1 "2015-05-13T06:02:10Z")

</div>

hi,

we have a percolation miss problem described in this post  
[http://stackoverflow.com/questions/30194246/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re](http://stackoverflow.com/questions/30194246/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re) and  
probably related with this issue  
[https://github.com/elastic/elasticsearch/issues/10722](https://github.com/elastic/elasticsearch/issues/10722).

you can reproduce problem using this script

> <https://gist.github.com/ekesken/de41598a1e7e54c6f33c>

at least we need a workaround for now, because missing content is not  
acceptable for us. is there a way to check if every shard is really OK from  
code before sending percolation requests? obviously checking green status  
does not work.

/ekesken

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

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/5276971a-a884-4313-a3eb-8d175e2d46e9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5276971a-a884-4313-a3eb-8d175e2d46e9%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**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:14am UTC](https://discuss.elastic.co/t/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re-sizing/23616/2 "2017-07-06T00:14:22Z")

</div>