[SERVER-70580] Data race when accessing the ShardingDDLCoordinator's document metadata Created: 14/Oct/22 Updated: 29/Oct/23 Resolved: 09/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Enrico Golfieri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2022-11-14 | ||||
| Participants: | |||||
| Linked BF Score: | 24 | ||||
| Description |
|
There is a lock that should be held before getting the coordinator's document metadata, to prevent a race with a concurrent thread that is setting the document. |
| Comments |
| Comment by Githook User [ 09/Nov/22 ] |
|
Author: {'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}Message: |