[DRILL-3052] canceling a fragment executor before it starts running will cause the Foreman to wait indefinitely for a terminal message from that fragment

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Assignee: Jacques Nadeau
• Reporter: Abdel Hakim Deneche
• Created: 13/May/15 03:57
• Updated: 03/Nov/21 11:29
• Resolved: 15/May/15 06:48

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.

Issue Links

• incorporates: DRILL-3072 Profile UI fails to load when there is an empty json profile
• incorporates: DRILL-3066 AtomicRemainder - Tried to close remainder, but it has already been closed.
• is fixed by: DRILL-8030 Intermittent TestDrillbitResilience cancelInMiddleOfFetchingResults and foreman_runTryEnd failures