You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Paul Merlin (JIRA)" <ji...@apache.org> on 2015/07/10 11:38:04 UTC
[jira] [Created] (ZEST-56) Intermittent failures of ElasticSearch
indexing on startup
Paul Merlin created ZEST-56:
-------------------------------
Summary: Intermittent failures of ElasticSearch indexing on startup
Key: ZEST-56
URL: https://issues.apache.org/jira/browse/ZEST-56
Project: Zest
Issue Type: Bug
Affects Versions: 2.0
Reporter: Paul Merlin
Assignee: Paul Merlin
Fix For: 2.1
ElasticSearch can take some time to get ready for queries and actual activation code do not wait for it's readiness.
If a query is sent to ES right after activation there's a chance it's not ready and one gets the following error: "Failed to execute phase [query], all shards failed".
This error pops up quite often when using embedded ES in unit tests.
To mitigate this we should, on activation:
- ensure the Qi4j index is refreshed
- wait for ES yellow status (the primary shard is allocated but replicas may not be)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)