[SERVER-46930] AutoGetOplog doesn't acquire collection IX lock correctly for non-document-locking engines Created: 18/Mar/20 Updated: 29/Oct/23 Resolved: 18/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||
| Sprint: | Repl 2020-03-23 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 50 | ||||||||||||||||
| Description |
|
In kLogOp mode, AutoGetOplog only acquires collection lock for non-document-locking storage engines if it is not already held. However, AutoGetOplog uses ShouldNotConflictWithSecondaryBatchApplicationBlock which makes isCollectionLockedForMode always return true, resulting in skipping collection lock for kLogOp mode under non-document-locking storage engines. |
| Comments |
| Comment by Githook User [ 14/Sep/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: validate command on the oplog collection (cherry picked from commit c15e8ae74071482d69179c7e5e5e6bdc882d2beb) |
| Comment by Githook User [ 18/Mar/20 ] |
|
Author: {'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}Message: |