[SERVER-42055] Only acquire a collection IX lock to write the lastVote document - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Critical - P2
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.6.14, 4.0.11, 4.2.0-rc3, 3.4.23, 4.3.1
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.2, v4.0, v3.6, v3.4
Sprint:
Repl 2019-07-15
Case:
Linked BF Score:
16

Description

This lock acquisition should be a collection IX, not a DB X. This will prevent elections from blocking behind other local database readers and writers. This is just a single document update and as a result shouldn't need a stronger lock. Before doing this we should check the history of this lock and see why it is so coarse grained.

Attachments

Issue Links

is related to

SERVER-48399 Writing config document to "local.system.replset" should not acquire database lock in stronger mode (X).

Backlog

related to

SERVER-30727 Secondary stuck in loop of current election

Closed

SERVER-42653 Always waitUntilDurable when writing lastVote document

Closed

tested by

SERVER-42056 Test that local db reads do not block elections or vote requests

Closed

Activity

People

Assignee:: Matthew Russotto

Reporter:: Judah Schvimer

Participants:: Andy Schwerin, David Bartley, Eric Milkie, Githook User, Judah Schvimer, Kelsey Schubert, Matthew Russotto

Votes:: 0 Vote for this issue

Watchers:: 13 Start watching this issue

Dates

Created:: Jul 02 2019 09:05:00 PM UTC

Updated:: Jun 18 2021 05:01:36 AM UTC

Resolved:: Jul 08 2019 08:09:39 PM UTC