[SERVER-42478] Remove DB MODE_X locks from oplog application of create/createIndexes Created: 29/Jul/19 Updated: 29/Oct/23 Resolved: 16/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | KS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||
| Steps To Reproduce: | Found by code inspection, no reproducer yet. |
||||||||||||
| Sprint: | Execution Team 2019-09-09, Execution Team 2019-09-23 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
In oplog application, there are still places (here and here) where we take MODE_X database locks. This could affect secondary read performance in presence of DDL operations on other collections in the same database. |
| Comments |
| Comment by Githook User [ 24/Sep/19 ] | |||||||||||||||||||||||||||||||
|
Author: {'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb'}Message: (cherry picked from commit 8357a1d76883e8a20c014c58c6b1feabffb91742) | |||||||||||||||||||||||||||||||
| Comment by Githook User [ 16/Sep/19 ] | |||||||||||||||||||||||||||||||
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: | |||||||||||||||||||||||||||||||
| Comment by Judah Schvimer [ 30/Jul/19 ] | |||||||||||||||||||||||||||||||
|
I also wonder if | |||||||||||||||||||||||||||||||
| Comment by Judah Schvimer [ 29/Jul/19 ] | |||||||||||||||||||||||||||||||
|
In theory something like this should be able to test it in concurrency_sharded_replication, but it hasn't reproduced:
|