[SERVER-50045] JournalFlusher can interrupt write concern with ShutdownInProgress during rollback Created: 31/Jul/20 Updated: 29/Oct/23 Resolved: 27/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||
| Sprint: | Execution Team 2020-09-07 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 11 | ||||||||||||||||
| Description |
|
This is both a problem because write_concern_after_stepdown.js expects a stepdown error code, and because it is semantically the wrong error code. Write concern waiting calls StorageControl::waitForJournalFlush(opCtx);. This does not have an interrupt point, though it will throw when the catalog is shutdown. We should either tell it what error code to throw when we shut down the catalog or make it interruptible. |
| Comments |
| Comment by Githook User [ 07/Apr/21 ] |
|
(Tracked in Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit a751610b2eb005c0b47f6ad637f009f8aa9c8346) |
| Comment by Githook User [ 09/Sep/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 27/Aug/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |