[SERVER-55745] The Fuzzer can run killOp on the JournalFlusher thread and cause it to throw an unexpected error Created: 02/Apr/21 Updated: 29/Oct/23 Resolved: 08/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| 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: | Execution Team 2021-04-19 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 152 | ||||||||||||||||||||
| Description |
|
The fuzzer appears to have run killOp against the journal flusher thread. At least, right after there's a log about killing op with opId 8221, the journal flusher gets interrupted with the same error message as OperationContext::checkForInterruptNoAssert, which can be called from the locking code (the journal flusher takes a lock to do a write to the oplogTruncateAfterPoint), can return. |
| Comments |
| Comment by Githook User [ 09/Apr/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 08/Apr/21 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |