[DOCS-12710] Docs for SERVER-41035: Rollback should kill all user operations before taking RSTL lock in X. Created: 19/May/19  Updated: 13/Nov/23  Resolved: 09/Aug/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.12, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-41035 Rollback should kill all user operati... Closed
Related
is related to DOCS-12717 Docs for SERVER-37574: Force reconfig... Closed
Participants:
Days since reply: 4 years, 26 weeks, 5 days ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

No documentation summary in engineering ticket

Engineering Ticket Description:

Currently, there is a  3 way deadlock. Assume that we are transitioning from secondary to rollback.

  • Thread A (Read thread)  acquires RSTL lock in IX and  blocked by a prepared txn due to prepare conflict.
  • Rollback enqueues RSTL lock in X mode. And blocked behind A.
  • Prepared txn won’t be able commit until we transition out of rollback.

Alternatively, thread A might have got blocked on prepared transaction due to conflicting DB/ collection lock. For eg. dbhash cmd.

EDIT: Blocked due to conflicting mongoDB locks  is not possible as secondary prepared txn yield mongoDB locks.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 09/Aug/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12717,DOCS-12710: 4.2 reconfig/rollback and inprogress user operations
Branch: master
https://github.com/mongodb/docs/commit/45a52477931ce75d6dcb40c65516b56f9d1414f0

Generated at Thu Feb 08 08:05:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.