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

Chun Chang commented on DRILL-1707:
-----------------------------------

This is what explain plan for generates in the drillbit.log of forman:

2014-11-13 16:19:57,030 [UserServer-1] DEBUG o.a.drill.exec.rpc.user.UserServer 
- Received query to run.  Returning query handle.
2014-11-13 16:19:57,072 [UserServer-1] WARN  
o.a.d.exec.work.foreman.QueryStatus - Update running or pending query state : 
PENDING
2014-11-13 16:19:57,089 [WorkManager Event Thread] DEBUG 
o.apache.drill.exec.work.WorkManager - Starting pending task 
org.apache.drill.exec.work.WorkManager$RunnableWrapper@288d0349
2014-11-13 16:19:57,090 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.h.HBaseStoragePluginConfig - Initializing HBase StoragePlugin 
configuration with zookeeper quorum 'null', port 'null'.
2014-11-13 16:19:57,091 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.h.HBaseStoragePluginConfig - Initializing HBase StoragePlugin 
configuration with zookeeper quorum 'null', port 'null'.
2014-11-13 16:19:57,096 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.h.HBaseStoragePluginConfig - Initializing HBase StoragePlugin 
configuration with zookeeper quorum '10.10.100.120', port '5181'.
2014-11-13 16:19:57,097 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.h.HBaseStoragePluginConfig - Initializing HBase StoragePlugin 
configuration with zookeeper quorum '10.10.100.120', port '5181'.
2014-11-13 16:19:57,098 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.drill.exec.store.SchemaFactory - Took 9 ms to register schemas.
2014-11-13 16:19:57,262 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.p.s.h.DefaultSqlHandler - Optiq Logical :
ProjectRel(c0=[$0], c1=[$1], c2=[$2], c3=[$3], m0=[$4]): rowcount = 
1.1390624999999999, cumulative cost = {1010425.059375 rows, 1000465.6484375 
cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 103
  AggregateRel(group=[{0, 1, 2, 3}], m0=[SUM($4)]): rowcount = 
1.1390624999999999, cumulative cost = {1010423.9203125 rows, 1000459.953125 
cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 101
    ProjectRel(c0=[$1], c1=[$2], c2=[$6], $f3=[ITEM($4, 'warehouse_id')], 
*0=[$4]): rowcount = 11.390624999999998, cumulative cost = {1010422.78125 rows, 
1000459.953125 cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 99
      FilterRel(condition=[AND(=(ITEM($4, 'time_id'), $3), =($1, 1997), =($2, 
'Q3'), =(ITEM($4, 'store_id'), $7), =($6, 'WA'), =(ITEM($4, 'warehouse_id'), 
2))]): rowcount = 11.390624999999998, cumulative cost = {1010411.390625 rows, 
1000403.0 cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 97
        JoinRel(condition=[true], joinType=[inner]): rowcount = 1000000.0, 
cumulative cost = {1010400.0 rows, 403.0 cpu, 0.0 io, 0.0 network, 0.0 memory}, 
id = 95
          JoinRel(condition=[true], joinType=[inner]): rowcount = 10000.0, 
cumulative cost = {10300.0 rows, 302.0 cpu, 0.0 io, 0.0 network, 0.0 memory}, 
id = 92
            EnumerableTableAccessRel(table=[[dfs, time_by_day]]): rowcount = 
100.0, cumulative cost = {100.0 rows, 101.0 cpu, 0.0 io, 0.0 network, 0.0 
memory}, id = 78
            ProjectRel(*=[$0]): rowcount = 100.0, cumulative cost = {200.0 
rows, 201.0 cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 90
              EnumerableTableAccessRel(table=[[dfs, inventory_fact_1997]]): 
rowcount = 100.0, cumulative cost = {100.0 rows, 101.0 cpu, 0.0 io, 0.0 
network, 0.0 memory}, id = 79
          EnumerableTableAccessRel(table=[[dfs, store]]): rowcount = 100.0, 
cumulative cost = {100.0 rows, 101.0 cpu, 0.0 io, 0.0 network, 0.0 memory}, id 
= 82

2014-11-13 16:19:57,371 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.parquet.ParquetGroupScan - rowGroupInfo path: 
/drill/testdata/mondrian/store start: 4 length 6179
2014-11-13 16:19:57,372 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.parquet.ParquetGroupScan - Took 9 ms to get row group infos
2014-11-13 16:19:57,541 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.parquet.ParquetGroupScan - rowGroupInfo path: 
/drill/testdata/mondrian/time_by_day start: 4 length 51585
2014-11-13 16:19:57,541 [2b6fe92a-cbb1-43c5-bbf5-577296465810:foreman] DEBUG 
o.a.d.e.s.parquet.ParquetGroupScan - Took 6 ms to get row group infos

> Regression: Mondrian query5843.q hangs
> --------------------------------------
>
>                 Key: DRILL-1707
>                 URL: https://issues.apache.org/jira/browse/DRILL-1707
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization
>    Affects Versions: 0.7.0
>            Reporter: Chun Chang
>            Priority: Blocker
>         Attachments: drillstack.txt
>
>
> #Thu Nov 13 13:47:45 EST 2014
> git.commit.id.abbrev=fd54e71
> The following Mondrian query hangs. It was working with previous release.
> 0: jdbc:drill:schema=dfs>
> SELECT time_by_day.the_year     AS c0, 
>        time_by_day.quarter      AS c1, 
>        store.store_state        AS c2, 
>        FACT.warehouse_id        AS c3, 
>        Sum(FACT.warehouse_cost) AS m0 
> FROM   time_by_day AS time_by_day, 
>        (SELECT * 
>         FROM   inventory_fact_1997 AS FOOBAR) AS FACT, 
>        store AS store 
> WHERE  FACT.time_id = time_by_day.time_id 
>        AND time_by_day.the_year = 1997 
>        AND time_by_day.quarter = 'Q3' 
>        AND FACT.store_id = store.store_id 
>        AND store.store_state = 'WA' 
>        AND FACT.warehouse_id = 2 
> GROUP  BY time_by_day.the_year, 
>           time_by_day.quarter, 
>           store.store_state, 
>           FACT.warehouse_id;
> The drillbit handles the query seems active with around 100% CPU usage but 
> the query never returns. The only log message found in drill bit.log is 
> following:
> 2014-11-13 15:07:14,426 [UserServer-1] WARN  
> o.a.d.exec.work.foreman.QueryStatus - Update running or pending query state : 
> PENDING
> Since this is a regression, marked as release blocker.



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

Reply via email to