You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Bruno Roustant (Jira)" <ji...@apache.org> on 2022/12/06 13:18:00 UTC

[jira] [Resolved] (SOLR-16473) Race condition in shard split when a sub-shard is put in recovery state

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

Bruno Roustant resolved SOLR-16473.
-----------------------------------
    Fix Version/s: 9.2
       Resolution: Fixed

> Race condition in shard split when a sub-shard is put in recovery state
> -----------------------------------------------------------------------
>
>                 Key: SOLR-16473
>                 URL: https://issues.apache.org/jira/browse/SOLR-16473
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Bruno Roustant
>            Assignee: Bruno Roustant
>            Priority: Major
>             Fix For: 9.2
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> There is a race condition in shard splits code when a sub-shard is put in RECOVERY state and the remaining replicas are added. The problem is that the code does not wait to ensure the sub-shard state is indeed changed to RECOVERY.
> [~andyvuong] reproduced the bug by adding some artificial delay, and this race condition seems to be the root cause of indexing holes.
> The fix is to wait for the RECOVERY state.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org