Call afterWriteOperation in testShouldFlushAfterPeerRecovery

dnhatn · Aug 5, 2019 · 0f2b3a1 · 0f2b3a1
1 parent 6e2e73b
commit 0f2b3a1
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/server/src/test/java/org/elasticsearch/indices/recovery/RecoveryTests.java b/server/src/test/java/org/elasticsearch/indices/recovery/RecoveryTests.java
@@ -412,7 +412,9 @@ public void testShouldFlushAfterPeerRecovery() throws Exception {
             replica.indexSettings().updateIndexMetaData(builder.build());
             replica.onSettingsChanged();
             shards.recoverReplica(replica);
-            // Make sure the flushing will eventually be completed (eg. `shouldPeriodicallyFlush` is false)
+            // trigger a flush if `shouldPeriodicallyFlush` becomes true after we roll a new generation in RecoveryTarget#finalizeRecovery
+            replica.afterWriteOperation();
+            // Make sure that the flushing loop will eventually complete (i.e, `shouldPeriodicallyFlush` becomes false)
             assertBusy(() -> assertThat(getEngine(replica).shouldPeriodicallyFlush(), equalTo(false)));
             boolean softDeletesEnabled = replica.indexSettings().isSoftDeleteEnabled();
             assertThat(getTranslog(replica).totalOperations(), equalTo(softDeletesEnabled ? 0 : numDocs));