-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.4, v4.2
-
Repl 2020-06-01
-
12
In transactions_during_step_down.js, we start a transaction, which gets aborted by a stepdown. However, since we never abort the transaction in the shell, when the session goes out of scope and garbage collection runs, we run endSession(), which will run abortTransaction against the server. This can hang and lead to deadlock if we are in the process of stopping the ReplSetTest and have fsynclocked the server.