[SERVER-84668] Avoid tenant lock upgrade when applying change collection creation oplog entry Created: 09/Jan/24 Updated: 09/Jan/24 Resolved: 09/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2024-01-22 | ||||||||
| Participants: | |||||||||
| Description |
|
When creating a change collection with a tenant id, the tenant X lock is taken. However if this is coming from oplog application, the tenant IX lock was already acquired. This results in a lock upgrade. |
| Comments |
| Comment by Githook User [ 09/Jan/24 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: GitOrigin-RevId: 741d3fea198fa479e9595e75f34554ddc8e49ce9 |