You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2015/05/08 01:32:59 UTC

[jira] [Created] (DRILL-2989) TPCDS Query corrupts Drillbits and causing subsequent unrelated queries to hang (and timeout)

Kunal Khatua created DRILL-2989:
-----------------------------------

             Summary: 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


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)