-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-08-10, Repl 2020-08-24
In the ReplSetTest.awaitSecondaryNodesForRollbackTest function, we first call awaitSecondaryNodes, and if that times out, we then enter this section of logic to check for an unrecoverable rollback scenario. If the first awaitSecondaryNodes call times out, though, we trigger the hang analyzer which will suspend the mongod processes that we attach to. This prevents us from connecting to the nodes to run commands to check for unrecoverability. We should disable the hang analyzer for this awaitSecondaryNodes call (we can consider using MongoRunner.runHangAnalyzer.disable()), so that we can still connect to and run commands against nodes even after it times out.
- is duplicated by
-
SERVER-50048 minValid on another branch of history is unrecoverable but not detected
- Closed
- related to
-
SERVER-43867 Work around unrecoverability of rollback via refetch in tests
- Closed
-
SERVER-49167 Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=false
- Closed