-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.2, v4.0
-
Repl 2019-08-26, Repl 2019-09-09
-
12
We have relatively sparse logging inside ReplSetTest.stopSet, which can make it hard to understand which parts of the function are currently running or whether certain branches were taken at all. We could add log messages to indicate the following information:
- The beginning of stopSet
- Before each type of consistency check
- Whether we ran the consistency checks at all
- Before running the waitForStepDownOnNonCommandShutdown command
- Before stopping all nodes
- If the call was forRestart