[SERVER-51714] Avoid crashing mongod when network setup fails Created: 16/Oct/20 Updated: 27/Oct/23 Resolved: 25/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Amirsaman Memaripour |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Service arch 2020-11-30 | ||||
| Participants: | |||||
| Linked BF Score: | 29 | ||||
| Description |
|
The order of initializing the global storage engine for mongod v3.6 could cause the process to crash if the attempt to setup TransportLayerManager fails (here). This is an issue due to this assumption for creating a new opCtx, that a global storage engine is available. The shutdown code, in particular here, may attempt to create a new opCtx, which would result in violating the invariant. This ticket should address the issue by making sure the process exits cleanly if the network setup fails. |
| Comments |
| Comment by Amirsaman Memaripour [ 25/Nov/20 ] |
|
Fixes for |