Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When a Foreman receives a cancellation from the client it will cancel all it's fragments and go into a CANCELLATION_REQUEST state. Each fragment will cancel it's work, close it's resources and report a terminal state to the Foreman (either CANCELLED or FAILED). The Foreman will wait for all fragments to report before sending a terminal message to the client.
If a fragment is cancelled before it started running (similar to DRILL-2878) it will close it's resources but it will never send a terminal state to the foreman which will cause the foreman to wait indefinitely.
Attachments
Attachments
Issue Links
- incorporates
-
DRILL-3072 Profile UI fails to load when there is an empty json profile
- Closed
-
DRILL-3066 AtomicRemainder - Tried to close remainder, but it has already been closed.
- Closed
- is fixed by
-
DRILL-8030 Intermittent TestDrillbitResilience cancelInMiddleOfFetchingResults and foreman_runTryEnd failures
- Resolved