Skip to content

Commit

Permalink
No longer unidle shard during recovery
Browse files Browse the repository at this point in the history
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
  • Loading branch information
jasontedor authored Dec 11, 2017
1 parent 1cd5575 commit 6bc40e4
Showing 1 changed file with 0 additions and 5 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -1745,11 +1745,6 @@ public void waitForOpsToComplete(final long seqNo) throws InterruptedException {
public void initiateTracking(final String allocationId) {
verifyPrimary();
getEngine().seqNoService().initiateTracking(allocationId);
/*
* 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
* the replica; mark our self as active to force a future background sync.
*/
active.compareAndSet(false, true);
}

/**
Expand Down

0 comments on commit 6bc40e4

Please sign in to comment.