[SERVER-73431] Potential segmentation fault on BalancerScheduler (investigation) Created: 30/Jan/23 Updated: 03/Feb/23 Resolved: 03/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Silvia Surroca |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2023-02-06 |
| Participants: |
| Description |
|
There is a potential segmentation fault when the BalancerScheduler submits a remote request. On BalancerCommandsSchedulerImpl::_submit method, we are sending a fire and forget request with an opCtx pointer attached to the request that goes out of scope right after sending the request. However, there is no occurrence of this failure, probably because the scheduler has been faster than the deletion of the OperationContext so far. |