No aggregation results unless more than half the shards are successful?

Dominik_Stadler · December 4, 2017, 11:48am

Hi,

I just would like to confirm and find documentation/description about something that we noticed (and had to invest a bit of time to actually understand).

We had a case where some indices had an incorrect mapping which caused some shards to fail, while others could execute the query successfully.

What was strange was that sometimes we got no results at all and sometimes at least results from the successful shards were returned. After some looking at this, we discovered that it seems to be related to the number of failed and successful shards. It seems only if more shards are successful than failed, aggregation results are returned, otherwise not.

Is this expected? Is this documented somewhere? Couldn't find any description of this, but would like to verify so we can act accordingly in this case.

This is with Elasticsearch 5.3.3, indices typically have 6 shards, between 3 and 20 indices are included in the queries.

This query returns values, 6 successful, 3 failed:
2017-12-04 07:00:31 UTC WARNING [<0x4>] [SearchResponseFutureImpl] 3 shard(s) failed in Elasticsearch SearchResponse while executing query on indexes [abc1 abc2, abc3] (96ms/99ms), hits: 72598, successful/failed shards: 6/3. Failure(s):

This query does not return any value at all because index abc4 adds more failing shards so that we have 6 successful and 6 failed:
2017-12-03 22:34:32 UTC WARNING [<0x4>] [SearchResponseFutureImpl] 6 shard(s) failed in Elasticsearch SearchResponse while executing query on indexes [abc1, abc2, abc3, abc4] (73ms/77ms), hits: 71703, successful/failed shards: 6/6. Failure(s):

Mark_Harwood · December 4, 2017, 1:35pm

I'm not aware of this logic. Returning results even if they are partial is the objective, however we are moving towards a policy of returning no results and an error in future versions if there's any reason for missing responses - see New query flag: allow_partial_results with default set to true. · Issue #27435 · elastic/elasticsearch · GitHub

Dominik_Stadler · December 4, 2017, 4:09pm

It looked fairly definite to us, more successfull shards than failed ones made it return data, otherwise not. Unless we did overlook something in our own logic on top of Elasticsearch, naturally.

Thanks, for the response and issue-link, it looks like we are currently "halfway there", kind of

Mark_Harwood · December 4, 2017, 4:28pm

Maybe some shards are "skipped" because they don't contain data relevant to the query and of the remaining non-skipped shards these all failed triggering this failure condition:

github.com

elastic/elasticsearch/blob/6319424e4ab08a440f6dbb936f3c31cdb8b01590/core/src/main/java/org/elasticsearch/action/search/AbstractSearchAsyncAction.java#L124


        return;
    }
    executePhase(this);
}


@Override
public final void executeNextPhase(SearchPhase currentPhase, SearchPhase nextPhase) {
    /* This is the main search phase transition where we move to the next phase. At this point we check if there is
     * at least one successful operation left and if so we move to the next phase. If not we immediately fail the
     * search phase as "all shards failed"*/
    if (successfulOps.get() == 0) { // we have 0 successful results that means we shortcut stuff and return a failure
        if (logger.isDebugEnabled()) {
            final ShardOperationFailedException[] shardSearchFailures = ExceptionsHelper.groupBy(buildShardFailures());
            Throwable cause = shardSearchFailures.length == 0 ? null :
                ElasticsearchException.guessRootCauses(shardSearchFailures[0].getCause())[0];
            logger.debug((Supplier<?>) () -> new ParameterizedMessage("All shards failed for phase: [{}]", getName()),
                cause);
        }
        onPhaseFailure(currentPhase, "all shards failed", null);
    } else {
        if (logger.isTraceEnabled()) {

system · January 1, 2018, 4:28pm

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Elasticsearch 6.5 returns serch results with some shards reported as failed Elasticsearch	1	320	October 7, 2019
Search to only return when all shards are successful Elasticsearch	3	647	December 6, 2017
Failed shards in search response, but no reasons Elasticsearch	1	338	July 6, 2017
Reproduce 206 Partial result Elasticsearch	4	1030	May 19, 2021
How do people typically handle shard failures in their results? Elasticsearch	6	14383	July 6, 2017

No aggregation results unless more than half the shards are successful?

Related topics