You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Sudheesh Katkam (JIRA)" <ji...@apache.org> on 2015/05/27 00:05:17 UTC

[jira] [Updated] (DRILL-3190) Invalid FragmentState transition from CANCELLATION_REQUESTED in QueryManager

     [ https://issues.apache.org/jira/browse/DRILL-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudheesh Katkam updated DRILL-3190:
-----------------------------------
    Attachment: DRILL-3190.1.patch.txt

> Invalid FragmentState transition from CANCELLATION_REQUESTED in QueryManager
> ----------------------------------------------------------------------------
>
>                 Key: DRILL-3190
>                 URL: https://issues.apache.org/jira/browse/DRILL-3190
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>            Reporter: Sudheesh Katkam
>            Assignee: Sudheesh Katkam
>             Fix For: 1.1.0
>
>         Attachments: DRILL-3190.1.patch.txt
>
>
> If a fragment is cancelled as soon as it starts running, there are two state change messages that are reported to the QueryManager: transition to RUNNING and transition to CANCELLATION_REQUESTED. 
> The order of receiving these messages is not guaranteed because the messages *can be* reported from different threads. The QueryManager#FragmentStateListener does not check for a transition from CANCELLATION_REQUESTED to RUNNING. This state change should not happen in FragmentData#setStatus.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)