-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Programmability
-
ALL
-
0
-
5
Implementations of TaskExecutor::scheduleWork are required not to move-from their provided 'work' CallbackFn when returning a non-ok status. This requirement is relied on in TaskExecutor::schedule to call the callback with the non-ok status returned from scheduleWork.
ScopedTaskExecutor is violating this contract and moving-from the provided work callback even when returning a non-ok Status from scheduleWork. We have evidence of this happening from build failures. While not confirmed, the likely culprit is this line. We need to fix this or else risk triggering this invariant in production runs.
- related to
-
SERVER-50619 Make sure to shut down ScopedTaskExecutor before shutting down parent executor in PrimaryOnlyService
- Closed
-
SERVER-78971 Skip shutting down Grid::getExecutorPool() when TestProctor is disabled
- Closed
-
SERVER-51079 Work around SERVER-50612 in PrimaryOnlyServiceTest::StepUpAfterShutdown
- Closed
-
SERVER-62220 Complete TODO listed in SERVER-50612
- Closed