You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2019/12/28 00:17:00 UTC
[jira] [Updated] (IMPALA-9267) Impala hits DCHECK in
ClientRequestState due to invalid state transition
[ https://issues.apache.org/jira/browse/IMPALA-9267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell updated IMPALA-9267:
----------------------------------
Attachment: backtrace.txt
> 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
> Priority: Blocker
> Labels: broken-build
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org