[jira] [Resolved] (IMPALA-9267) Impala hits DCHECK in ClientRequestState due to invalid state transition

["Sahil Takiar (Jira)" <ji...@apache.org>]

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

Sahil Takiar resolved IMPALA-9267.
----------------------------------
    Fix Version/s: Impala 3.4.0
       Resolution: Fixed

> Impala hits DCHECK in ClientRequestState due to invalid state transition
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-9267
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9267
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 3.4.0
>            Reporter: Joe McDonnell
>            Assignee: Sahil Takiar
>            Priority: Blocker
>              Labels: broken-build
>             Fix For: Impala 3.4.0
>
>         Attachments: backtrace.txt
>
>
> Some test runs see the coordinator Impalad hit this DCHECK:
> {code:java}
> case ExecState::FINISHED:
>   // A query can transition from PENDING to FINISHED if it is cancelled by the
>   // client.
>   DCHECK(old_state == ExecState::PENDING || old_state == ExecState::RUNNING)
>       << Substitute(
>           error_msg, ExecStateToString(old_state), ExecStateToString(new_state));
>   UpdateExecState(new_state);
>   break;{code}
> The error message is:
> {noformat}
> F1222 23:01:14.020613 10494 client-request-state.cc:951] Check failed: old_state == ExecState::PENDING || old_state == ExecState::RUNNING Illegal state transition: ERROR -> FINISHED{noformat}
> This happened on one exhaustive run on Centos6 and an s3 run. There doesn't seem to be a pattern, so I'm assuming this is a generic issue.



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