Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Date: Fri, 10 Jul 2015 09:39:04 +0000 (UTC)
From: "Paul Merlin (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12844090.1436521068000.152707.1436521144522@Atlassian.JIRA>
In-Reply-To: <JIRA.12844090.1436521068000@Atlassian.JIRA>
References: <JIRA.12844090.1436521068000@Atlassian.JIRA>
 <JIRA.12844090.1436521068593@arcas>
Subject: [jira] [Resolved] (ZEST-56) Intermittent failures of ElasticSearch
 indexing on startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ZEST-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Merlin resolved ZEST-56.
-----------------------------
    Resolution: Fixed

> 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
>              Labels: elasticsearch, extensions, indexing
>             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)