[DRILL-6453] TPC-DS query 72 has regressed

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.14.0
• Fix Version/s: 1.15.0
• Component/s: Execution - Flow
• Labels: ready-to-commit
• Assignee: Timothy Farkas
• Reporter: Khurram Faraaz
• Reviewer: Boaz Ben-Zvi
• Created: 30/May/18 01:10
• Updated: 02/Oct/19 18:38
• Resolved: 13/Aug/18 11:58

Description

TPC-DS query 72 seems to have regressed, query profile for the case where it Canceled after 2 hours on Drill 1.14.0 is attached here.

On, Drill 1.14.0-SNAPSHOT 
commit : 931b43e (TPC-DS query 72 executed successfully on this commit, took around 55 seconds to execute)
SF1 parquet data on 4 nodes; 
planner.memory.max_query_memory_per_node = 10737418240. 
drill.exec.hashagg.fallback.enabled = true

TPC-DS query 72 executed successfully & took 47 seconds to complete execution.

TPC-DS data in the below run has date values stored as DATE datatype and not VARCHAR type

On, Drill 1.14.0-SNAPSHOT
commit : 82e1a12
SF1 parquet data on 4 nodes; 
planner.memory.max_query_memory_per_node = 10737418240. 
drill.exec.hashagg.fallback.enabled = true
and
alter system set `exec.hashjoin.num_partitions` = 1;

TPC-DS query 72 executed for 2 hrs and 11 mins and did not complete, I had to Cancel it by stopping the Foreman drillbit.
As a result several minor fragments are reported to be in CANCELLATION_REQUESTED state on UI.

Issue Links

• links to: GitHub Pull Request #1408