-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
The 'replSetResizeOplog' command does not take a global write lock anymore. It now uses an exclusive collection lock on the oplog collection.
Description of Linked Ticket
Remove global X lock acquisition for replSetResizeOplog. 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.)
- documents
-
SERVER-44029 Remove global X lock for replSetResizeOplog
- Closed