[SERVER-84118] Investigate where to reset FastClockSource in service context for mongos Created: 12/Dec/23 Updated: 13/Dec/23 Resolved: 12/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Evelyn Wu | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 5 | ||||||||||||
| Description |
|
Currently the fast clock source is set in the `main` function for mongos. But if shutdown happens too soon after startup, it is possible for the fast clock source to still have the default fast clock source from the constructor (here]). We might need to set the fast clock source earlier so that we won't be using the default one (which causes a segfault in the BF linked) |
| Comments |
| Comment by Phoebe Du [ 12/Dec/23 ] |
|
Issue is better described in Server-51055 and we'll try to solve the issue in there |