Skip to content

Commit 6bc40e4

Browse files
authored
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 1cd5575 commit 6bc40e4

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
@@ -1745,11 +1745,6 @@ public void waitForOpsToComplete(final long seqNo) throws InterruptedException {
17451745
public void initiateTracking(final String allocationId) {
17461746
verifyPrimary();
17471747
getEngine().seqNoService().initiateTracking(allocationId);
1748-
/*
1749-
* 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
1750-
* the replica; mark our self as active to force a future background sync.
1751-
*/
1752-
active.compareAndSet(false, true);
17531748
}
17541749

17551750
/**

0 commit comments

Comments
 (0)