drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deneche A. Hakim (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-4296) Query hangs in CANCELLATION_REQUESTED when cancelled after it starts returning results
Date Thu, 21 Jan 2016 19:23:39 GMT

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

Deneche A. Hakim updated DRILL-4296:
    Attachment: 295eefc3-8d15-d63b-a721-3fde365b639c.sys.drill

Attached jstack for both nodes. node1 is the Foreman node.
Also attached the query profile for the hanging query (saved from the web UI)
Heap dumps are too big (>300MB compressed) to be attached here

> Query hangs in CANCELLATION_REQUESTED when cancelled after it starts returning results
> --------------------------------------------------------------------------------------
>                 Key: DRILL-4296
>                 URL: https://issues.apache.org/jira/browse/DRILL-4296
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>    Affects Versions: 1.5.0
>         Environment: commit.id=c9dbfbd
> 2 nodes with 32 cores and 32GB of max direct memory for drill
>            Reporter: Deneche A. Hakim
>         Attachments: 295eefc3-8d15-d63b-a721-3fde365b639c.sys.drill, node1_jstack.txt,
> After running the following queries (it's the same reproduction from DRILL-2274):
> {noformat}
> set planner.memory.max_query_memory_per_node=8589934592;
> select sub1.uid from `all2274.json` sub1 inner join `all2274.json` sub2 on sub1.uid =
sub2.uid order by sub1.uid;
> {noformat}
> After the query starts returning results, I cancelled the query from sqlline. This caused
the query to hang in a CANCELLATION_REQUESTED state.
> Looking at jstack (attached) the root fragment is blocked waiting for Ack from the client.
> The the foreman node (which also runs Zookeeper) runs out of disk space once the query
finishes spilling, which seems to contribute to the issue. Once I changed the spill directory
to nfs I no longer so the issue.

This message was sent by Atlassian JIRA

View raw message