[SERVER-42865] Synchronize access to _shuttingDown in WiredTigerOplogManager Created: 16/Aug/19 Updated: 27/Oct/23 Resolved: 14/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Evgeni Dobranov |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2019-10-21 | ||||
| Participants: | |||||
| Linked BF Score: | 17 | ||||
| Description |
|
The value of _shuttingDown decides the validity of oplogRecordStore pointer: when _shuttingDown is true, oplogRecordStore is very likely (there is a small window) to be destroyed. However, we don't have any mutex to protect _shuttingDown here. It's possible that _shuttingDown gets set to true while this expression is being evaluated. |