From 6bc40e4bd389451aaec0e5900b43733439fb1dba Mon Sep 17 00:00:00 2001 From: Jason Tedor Date: Mon, 11 Dec 2017 13:26:27 -0500 Subject: [PATCH] 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 --- .../main/java/org/elasticsearch/index/shard/IndexShard.java | 5 ----- 1 file changed, 5 deletions(-) diff --git a/core/src/main/java/org/elasticsearch/index/shard/IndexShard.java b/core/src/main/java/org/elasticsearch/index/shard/IndexShard.java index f0246060acf5d..b3847cd1b4d02 100644 --- a/core/src/main/java/org/elasticsearch/index/shard/IndexShard.java +++ b/core/src/main/java/org/elasticsearch/index/shard/IndexShard.java @@ -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); } /**