Skip to content

Commit a4cb015

Browse files
committed
No longer unidle shard during recovery
Previously we would unidle a primary shard during recovery in case the recovery target would miss a background global checkpoint sync. However, the background global checkpoint syncs are no longer tied to the primary shard falling idle and so this unidling is no longer needed. Relates #27757
1 parent 59ee299 commit a4cb015

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

core/src/main/java/org/elasticsearch/index/shard/IndexShard.java

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1755,11 +1755,6 @@ public void waitForOpsToComplete(final long seqNo) throws InterruptedException {
17551755
public void initiateTracking(final String allocationId) {
17561756
verifyPrimary();
17571757
getEngine().seqNoService().initiateTracking(allocationId);
1758-
/*
1759-
* We could have blocked so long waiting for the replica to catch up that we fell idle and there will not be a background sync to
1760-
* the replica; mark our self as active to force a future background sync.
1761-
*/
1762-
active.compareAndSet(false, true);
17631758
}
17641759

17651760
/**

0 commit comments

Comments
 (0)