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

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 and
probably related with this issue
https://github.com/elastic/elasticsearch/issues/10722.

you can reproduce problem using this script

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/

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5276971a-a884-4313-a3eb-8d175e2d46e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.