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


we have a percolation miss problem described in this post and
probably related with this issue

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.


Please update your bookmarks! We have moved to

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
To view this discussion on the web visit
For more options, visit