[
https://issues.apache.org/jira/browse/DRILL-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Challapalli updated DRILL-5500:
-------------------------------------
Attachment: jstack.txt
drillbit.log
26ec8d41-c504-1096-39a4-aa61346c6e76.sys.drill
> Query hung in CANCELLATION_REQUESTED state
> ------------------------------------------
>
> Key: DRILL-5500
> URL: https://issues.apache.org/jira/browse/DRILL-5500
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 1.10.0
> Reporter: Rahul Challapalli
> Attachments: 26ec8d41-c504-1096-39a4-aa61346c6e76.sys.drill,
> drillbit.log, jstack.txt
>
>
> git.commit.id.abbrev=1e0a14c
> I cancelled the below query after ~17 minutes and the profiles indicated that
> the cancellation did not complete
> {code}
> alter session set `planner.enable_decimal_data_type` = true;
> alter session set `planner.slice_target` = 300;
> ALTER SESSION SET `exec.sort.disable_managed` = false;
> alter session set `planner.width.max_per_node` = 17;
> alter session set `planner.width.max_per_query` = 17;
> alter session set `planner.memory.max_query_memory_per_node` = 11926000000;
> select count(*) from (select * from
> dfs.`/drill/testdata/resource-manager/5kwidecolumns_500k.tbl` order by
> columns[0]) d where d.columns[0] = '4041054511';
> {code}
> ~1 minute after the cancellation has been issued, I took the jstack output
> and it indicated that some fragments are running. The sort operator in the
> query did not yet start any spilling by the time I issued the cancel request.
> I attached the query profile, log files and the jstack output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
