[ https://issues.apache.org/jira/browse/SOLR-16473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643460#comment-17643460 ]
ASF subversion and git services commented on SOLR-16473: -------------------------------------------------------- Commit 4519c1fcb050c4b2bbcb21e3c2583455fbfdb3a2 in solr's branch refs/heads/main from Bruno Roustant [ https://gitbox.apache.org/repos/asf?p=solr.git;h=4519c1fcb05 ] SOLR-16473: Fix race condition in shard split when a sub-shard is put in recovery state. Co-authored-by: Andy Vuong <a.vu...@salesforce.com> > 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 > 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-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org