# Percolate returns empty matches under heavy load during elasticsearch cluster re-sizing **URL:** \ **Category:** Elasticsearch\ **Created:** [May 13, 2015, 6:03am UTC](https://discuss.elastic.co/t/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re-sizing/594 "2015-05-13T06:03:19Z")\ **Posts on this page:** 2\ **Page:** 1
**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:03am UTC](https://discuss.elastic.co/t/percolate-returns-empty-matches-under-heavy-load-during-elasticsearch-cluster-re-sizing/594/1 "2015-05-13T06:03:19Z")
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](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 ---
**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/594/2 "2017-07-06T00:14:21Z")