-
Type: Task
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
17
The test gets flaky due to logging instability problem. We enable the fail point here and check the logs here to verify if we have hit the failpoint. If the logging is bottlenecked, then the test fails with checkLog.contains() getting timed out.
- depends on
-
SERVER-39165 Add waitForFailpoint command
- Closed
-
SERVER-42308 Improve synchronization between two fail points
- Backlog