You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Mala Chikka Kempanna (JIRA)" <ji...@apache.org> on 2017/05/05 20:45:04 UTC
[jira] [Created] (IMPALA-5285) Entire time of query begin-end
duration is not accounted for in summary
Mala Chikka Kempanna created IMPALA-5285:
--------------------------------------------
Summary: Entire time of query begin-end duration is not accounted for in summary
Key: IMPALA-5285
URL: https://issues.apache.org/jira/browse/IMPALA-5285
Project: IMPALA
Issue Type: Bug
Reporter: Mala Chikka Kempanna
Entire time of query begin-end duration is not accounted for in summary(This is excluding client fetch wait timer)
For eg
1) Start end time is
Start Time: 2017-03-24 09:23:03.131144000
End Time: 2017-03-24 10:54:57.702228000
2) Query exec summary and timelines look like below
{code}
Admission result: Admitted immediately
ExecSummary:
Operator #Hosts Avg Time Max Time #Rows Est. #Rows Peak Mem Est. Peak Mem Detail
---------------------------------------------------------------------------------------------------------------------
04:EXCHANGE 1 17.320us 17.320us 0 1.18B 0 -1.00 B UNPARTITIONED
03:AGGREGATE 18 4m35s 5m54s 0 1.18B 5.01 GB 5.99 GB FINALIZE
02:EXCHANGE 18 5s530ms 7s483ms 1.18B 1.18B 0 0 HASH(TRADEDATE,SYMB,EVENTID)
01:AGGREGATE 18 39s865ms 59s336ms 1.18B 1.18B 170.09 MB 56.95 GB STREAMING
00:SCAN HDFS 18 7s721ms 18s678ms 1.18B 1.18B 213.28 MB 264.00 MB cif20.dlereference
- ComputeScanRangeAssignmentTimer: 835228
- InactiveTotalTime: 0
- TotalTime: 0
Planner Timeline
Analysis finished: 1768171
Equivalence classes computed: 1953496
Single node plan created: 2636132
Runtime filters computed: 2764237
Distributed plan created: 3178894
Lineage info computed: 3297595
Planning finished: 4567814
Query Timeline
Query submitted: 315704
Planning finished: 8032272
Submit for admission: 10787376
Completed admission: 11053424
Ready to start 37 fragment instances: 12622968
All 37 fragment instances started: 591275200
Rows available: 5514496400348
First row fetched: 5514558703092
Unregister query: 5514571011444
ImpalaServer
- ClientFetchWaitTimer: 68269916
- InactiveTotalTime: 0
- RowMaterializationTimer: 6332212
- TotalTime: 0
{code}
I want to call attention to large discrepancy in total time accounted for in summary and timeline to one recorded ad start-end time
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)