Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 8 May 2015 23:37:02 +0000 (UTC)
From: "Kunal Khatua (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12828191.1431041531000.60330.1431128222005@Atlassian.JIRA>
In-Reply-To: <JIRA.12828191.1431041531000@Atlassian.JIRA>
References: <JIRA.12828191.1431041531000@Atlassian.JIRA>
 <JIRA.12828191.1431041531506@arcas>
Subject: [jira] [Commented] (DRILL-2989) TPCDS Query corrupts Drillbits and
 causing subsequent unrelated queries to hang (and timeout)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DRILL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535896#comment-14535896 ] 

Kunal Khatua commented on DRILL-2989:
-------------------------------------

Added hung JDBC Client App's JStack as well. 
The JDBC Client communicated with the foreman on ucs-node6 (out of all the 30 nodes ranging from ucs-node2 to node31)

The DRILL-2989.out is the client's output log.

We see that the query timed out when attempting to fetch rows for the TPCDS query. 
After that...the Drillbits are rendered unusable.


> TPCDS Query corrupts Drillbits and causing subsequent unrelated queries to hang (and timeout)
> ---------------------------------------------------------------------------------------------
>
>                 Key: DRILL-2989
>                 URL: https://issues.apache.org/jira/browse/DRILL-2989
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>         Environment: RHEL 6.4
>            Reporter: Kunal Khatua
>            Priority: Critical
>             Fix For: 1.0.0
>
>         Attachments: dBit_TPC-DBug.jstack.out
>
>
> 30-node setup has TPC-H Drill (SF100) and TPC-DS Drill (SF100) in two different workspaces.
> TPC-H Query 6 is executed on the cluster successfully, followed by execution of TPC-DS Query 2; which hangs during the executeQuery() operation. After a 2min timeout, the TPC-H Query is executed on the cluster, but this also hangs during the fetching of rows from the ResultSet. The profile page for the second attempt at TPC-H query 6 shows it as pending.
> The TPC-H schema is in its own workspace which exposes the directories as tables.
> The TPC-DS schema is in its own workspace, which has views on top of the directories containing the actual tables' data.
> ====TPCH-06====
> [INFO] Will be using Drillbit on 10.10.120.114
> [QUERYID] 2ab41296-1420-ee4b-2617-849b63eb11b4
> [STAT] TOTAL TIME : 7420 msec
> ====TPCDS-02====
> [INFO] Will be using Drillbit on 10.10.120.117
> [TIME OUT] Query took more than 120 sec.
> ====TPCH-06====
> [INFO] Will be using Drillbit on 10.10.120.130
> [TIME OUT] Query took more than 120 sec.
> [QUERYID] 2ab41027-abcc-c48a-7e3c-957bb069f452
> [STAT] TOTAL TIME : 120017 msec


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)