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
This commit is contained in:
Jason Tedor 2017-12-11 13:26:27 -05:00 committed by GitHub
parent 1cd5575997
commit 6bc40e4bd3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 5 deletions

View File

@ -1745,11 +1745,6 @@ public class IndexShard extends AbstractIndexShardComponent implements IndicesCl
public void initiateTracking(final String allocationId) { public void initiateTracking(final String allocationId) {
verifyPrimary(); verifyPrimary();
getEngine().seqNoService().initiateTracking(allocationId); 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);
} }
/** /**