Details
-
Bug
-
Status: Open
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
Replication
-
ALL
-
6
Description
Acquiring the global lock in the initAndListen function while initialization mongod after starting up replication is dangerous as we might reconstruct a prepared transaction which acquire the global lock and keep it, which will cause a deadlock.
You can repro it by adding a sleep before this line and run jstests/replsets/ddl_op_behind_transaction_fails_in_shutdown.js
Attachments
Issue Links
- is caused by
-
SERVER-56644 local.system.resharding.slimOplogForGraphLookup isn't created when replica set has already been initiated
-
- Closed
-
- related to
-
SERVER-67605 Make retryable_findAndModify_commit_and_abort_prepared_txns_after_failover_and_restart.js not test restart with a 1-node shard
-
- Closed
-