drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Challapalli (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-5466) Cancelling a query caused "DrillBuf refCnt has gone negative" error
Date Tue, 02 May 2017 23:17:04 GMT
Rahul Challapalli created DRILL-5466:
----------------------------------------

             Summary: Cancelling a query caused "DrillBuf refCnt has gone negative" error
                 Key: DRILL-5466
                 URL: https://issues.apache.org/jira/browse/DRILL-5466
             Project: Apache Drill
          Issue Type: Bug
    Affects Versions: 1.10.0
            Reporter: Rahul Challapalli
         Attachments: createViewsParquet.sql, ref_negative.log, ref_negative.profile

git.commit.id.abbrev=38ef562

The below query was running on a tpcds sf1 data set. I cancelled it after 9 seconds and below
is the message I got
{code}
alter session set `planner.enable_decimal_data_type` = true;
ALTER SESSION SET `exec.sort.disable_managed` = false;
alter session set `planner.width.max_per_node` = 1;
alter session set `planner.disable_exchanges` = true;
alter session set `planner.width.max_per_query` = 1;
alter session set `planner.memory.max_query_memory_per_node` = 200435456;
alter session set `planner.enable_hashjoin` = false;
SELECT dt.d_year,
               item.i_brand_id          brand_id,
               item.i_brand             brand,
               Sum(ss_ext_discount_amt) sum_agg
FROM   date_dim dt,
       store_sales,
       item
WHERE  dt.d_date_sk = store_sales.ss_sold_date_sk
       AND store_sales.ss_item_sk = item.i_item_sk
       AND item.i_manufact_id = 427
       AND dt.d_moy = 11
GROUP  BY dt.d_year,
          item.i_brand,
          item.i_brand_id
ORDER  BY dt.d_year,
          sum_agg DESC,
          brand_id;
          
Error: Unexpected RuntimeException: java.lang.IllegalStateException: DrillBuf[7530] refCnt
has gone negative. Buffer Info: ledger[3661] allocator: ROOT), isOwning: false, size: 1, references:
-1, life: 8258809446482809..8258817912668200, allocatorManager: [3661, life: 8258809446399747..8258817913039953]
(state=,code=0)

{code}

Surprisingly there is no trace of the exception in the logs. I attached the log, profile,
and view definition files. Let me know if you have any questions

The data set can be downloaded from https://s3.amazonaws.com/apache-drill/files/tpcds/tpcds_sf1_parquet.tar.gz



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message