[DOCS-13191] Investigate changes in SERVER-44026: Remove global X lock for reIndex Created: 01/Nov/19  Updated: 13/Nov/23  Resolved: 13/Jan/20

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

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: docs-administration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-44026 Remove global X lock for reIndex Closed
Participants:
Days since reply: 4 years, 4 weeks, 2 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

'reIndex' no longer takes a global lock. The strongest lock it now takes is an exclusive collection lock.

Description of Linked Ticket

Remove global X lock acquisition for reIndex. This is because acquiring global lock in X mode can be blocked by prepared transactions. The enqueued global X lock can block oplog queries which need the global IS lock. If these oplog queries and the data replication are needed to satisfy the prepared transaction's write concern, then the prepare transaction and replication cannot make progress. Thus a deadlock occurs.

Alternatively, if removing global X lock is not an option, deprecate the command or make sure it won't be blocked on prepare transactions.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 13/Jan/20 ]

Author:

{'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-13191, DOCS-13166, DOCS-13170: (v4.0 backport)

Comment by Githook User [ 13/Jan/20 ]

Author:

{'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-13191, DOCS-13166, DOCS-13170: remove global locks from reIndex, replSetResizeOplog, renameCollection

Comment by Ravind Kumar (Inactive) [ 01/Nov/19 ]

BACKPORT-5503

 

Backport waiting approval. If it goes through, this is 4.2+. If it does not go through, 4.4+.

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