-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
ALL
-
Repl 2025-06-09, Repl 2025-06-23
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
0
If primary stepdown occurs after an internal transaction has started and obtained the global locks, DB, and coll locks, it is not correctly yielding them when the transaction is interrupted. This is causing an invariant failure when its TxnResourceStash and locker is being destroyed. The transaction thread needs to explicitly release the locks/stash during exit, ensuring locker->unlock() is getting called, as they are currently remaining in scope and not being destroyed after the thread exits. See BF-37165 for a more detailed description of the issue.