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

["Vitalii Diravka (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437899#comment-17437899 ] 

Vitalii Diravka commented on DRILL-3052:
----------------------------------------

Move the comment from code to Jira history:
{code:java}
// DRILL-3052: Since root fragment is waiting on data and leaf fragments are cancelled before they send any
// data to root, root will never run. This test will timeout if the root did not send the final state to Foreman.
{code}
Actually the issue is resolved in DRILL-7973 by adding Thread.sleep(1000) before starting _CancellingThread_ thread.

> canceling a fragment executor before it starts running will cause the Foreman to wait indefinitely for a terminal message from that fragment
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-3052
>                 URL: https://issues.apache.org/jira/browse/DRILL-3052
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Abdel Hakim Deneche
>            Assignee: Jacques Nadeau
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: DRILL-3052.1.patch.txt
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)