[SERVER-69152] Introduce better concurrency control around setting LSID on OperationContext Created: 25/Aug/22 Updated: 29/Oct/23 Resolved: 08/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Amirsaman Memaripour |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tsan | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Service Arch 2022-11-14, Service Arch 2022-11-28, Service Arch 2022-12-12 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 11 | ||||||||||||
| Description |
|
Currently, readers such as killSessionsLocalKillOps will take the client lock, but writers will not (one example of many). Since the value of the LSID is not atomic, this is not a thread-safe access model. |
| Comments |
| Comment by Githook User [ 08/Dec/22 ] |
|
Author: {'name': 'Saman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |