You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Khurram Faraaz (JIRA)" <ji...@apache.org> on 2017/01/10 11:19:58 UTC
[jira] [Updated] (DRILL-5187) TPC-DS query 72 takes 32 minutes to
complete
[ https://issues.apache.org/jira/browse/DRILL-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Khurram Faraaz updated DRILL-5187:
----------------------------------
Description:
TPC-DS query takes close to 32 minutes to complete execution on a 4 node CentOS cluster, on Drill 1.10.0 against SF1 data.
Attached here are,
- query plan for query 72
- drillbit.log (has only query 72 information)
- JSON profile for query 72
- screen shot of fragment information from profiles tab on UI
HASH_JOIN operator takes 21minutes (fragment : 04-xx-53).
HASH_JOIN operator seems to be taking longer, it can be verified by looking at the profile information.
was:
TPC-DS query takes close to 32 minutes to complete execution on a 4 node CentOS cluster, on Drill 1.10.0 against SF1 data.
Attached here are,
- drillbit.log (has only query 72 information)
- JSON profile for query 72
- screen shot of fragment information from profiles tab on UI
HASH_JOIN operator takes 21minutes (fragment : 04-xx-53).
HASH_JOIN operator seems to be taking longer, it can be verified by looking at the profile information.
> TPC-DS query 72 takes 32 minutes to complete
> --------------------------------------------
>
> Key: DRILL-5187
> URL: https://issues.apache.org/jira/browse/DRILL-5187
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 1.10.0
> Environment: 4 node cluster
> Reporter: Khurram Faraaz
> Priority: Critical
> Attachments: quert72_query_plan.txt, query72_JSON_profile.txt, query72_drillbit.log, tpcds_query72_profile.png
>
>
> TPC-DS query takes close to 32 minutes to complete execution on a 4 node CentOS cluster, on Drill 1.10.0 against SF1 data.
> Attached here are,
> - query plan for query 72
> - drillbit.log (has only query 72 information)
> - JSON profile for query 72
> - screen shot of fragment information from profiles tab on UI
>
> HASH_JOIN operator takes 21minutes (fragment : 04-xx-53).
> HASH_JOIN operator seems to be taking longer, it can be verified by looking at the profile information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)