[
https://issues.apache.org/jira/browse/IMPALA-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558969#comment-16558969
]
Tim Armstrong commented on IMPALA-2371:
---------------------------------------
I can reproduce this with "select * from tpch_parquet.lineitem;" then
cancelling through the shell. I suspect this is something to do with when/how
the profile is serialised.
{noformat}
Query Runtime Profile:
Query (id=f349083b5f849b27:43c02d1000000000):
DEBUG MODE WARNING: Query profile created while running a DEBUG build of
Impala. Use RELEASE builds to measure query performance.
Summary:
Session ID: 6f496e12a7e982c2:4811c0d0fa7adf8e
Session Type: BEESWAX
Start Time: 2018-07-26 15:12:49.563652000
End Time: 2018-07-26 15:12:50.701983000
Query Type: QUERY
Query State: FINISHED
Query Status: OK
Impala Version: impalad version 3.1.0-SNAPSHOT DEBUG (build
cec33fa0ae75392668273d40b5a1bc4bbd7e9e2e)
User: tarmstrong
Connected User: tarmstrong
Delegated User:
Network Address: ::ffff:127.0.0.1:45250
Default Db: default
Sql Statement: select * from tpch_parquet.lineitem
Coordinator: tarmstrong-box:22000
Query Options (set by configuration):
Query Options (set by configuration and planner): MT_DOP=0
Plan:
...
Query Timeline: 1s139ms
- Query submitted: 106.243us (106.243us)
- Planning finished: 3.489ms (3.382ms)
- Submit for admission: 4.095ms (606.283us)
- Completed admission: 4.184ms (89.484us)
- Ready to start on 3 backends: 4.522ms (337.938us)
- All 3 execution backends (4 fragment instances) started: 9.615ms
(5.092ms)
- Rows available: 112.048ms (102.432ms)
- First row fetched: 211.207ms (99.158ms)
- Execution cancelled: 1s129ms (917.937ms)
- Released admission control resources: 1s137ms (8.720ms)
- Unregister query: 1s138ms (440.313us)
- ComputeScanRangeAssignmentTimer: 95.131us
{noformat}
> Query state/status of canelled query is reported as FINISHED/OK
> ---------------------------------------------------------------
>
> Key: IMPALA-2371
> URL: https://issues.apache.org/jira/browse/IMPALA-2371
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.2.4, Impala 2.3.0
> Reporter: Alan Choi
> Priority: Minor
> Labels: query-lifecycle, ramp-up
>
> *Problem Statement:*
> The query status should be "CANCELLED" if the query is cancelled. However,
> cancelling it through the shell does not do that. The query status still
> appear as ok:
> Query Type: QUERY
> Query State: FINISHED
> Query Status: OK
> This does not happen consistently and we don't know if there are any other
> conditions that result in this behavior. There is no known workaround.
> *Impact*
> It is impossible to tell, from the query profile status, whether the query
> finished successfully or not. It makes diagnosing query issue a lot harder.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
