[SERVER-83554] Fix data race between _doc access and _doc updates inside ConfigsvrCoordinator instances Created: 23/Nov/23 Updated: 08/Jan/24 Resolved: 01/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Silvia Surroca |
| 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 | ||||
| Sprint: | CAR Team 2023-11-27, CAR Team 2023-12-11 | ||||
| Participants: | |||||
| Linked BF Score: | 100 | ||||
| Description |
|
CurOp accesses the _doc document concurrently with all the updates that take place. Ideally we should protect data modification behind a mutex or some other protection to avoid reading invalid memory. |
| Comments |
| Comment by Githook User [ 01/Dec/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |