Skip to main content
Mogiking
Silver ⭐️
June 14, 2019
Solved

How can I check the Impala Query Execution Time?

Hello all,

My system administrator wants to check the Impala Query's execution time.

I can check the each fragment's total time in

[Cloudera Manager > Impala > Query > Query details].

But I can't find the total of query execution time.

 

Please anyone tell me where can I check it.

 

Thanks

EricL
EricLAnswer
Platinum ⭐️⭐️
June 19, 2019
Hi @Mogiking

Hue keeps the query handler open so that it can get back to its result during pagination. This is a feature in Hue, not a bug.

You can find that info from impala PROFILE under Query Timeline section, like below:

Query Timeline
Query submitted: 0ns (0)
Planning finished: 170ms (170000854)
Submit for admission: 172ms (172000864)
Completed admission: 172ms (172000864)
Ready to start on 2 backends: 172ms (172000864)
All 2 execution backends (3 fragment instances) started: 176ms (176000884)
Rows available: 422ms (422002119)
First row fetched: 501ms (501002515)
Unregister query: 509ms (509002555)

You can see detailed information on when data is available.

Cheers
Eric

4 replies

Andrew_Sherman
Gold ⭐️
Gold ⭐️
June 18, 2019

On that Cloudera Manager page, you can click 'Select Attributes' and check the box by 'Duration'.
Now any queries that are displayed will show the query duration in milliseconds.

Translate
Mogiking
MogikingAuthor
Silver ⭐️
June 18, 2019

Thanks for reply Andrew,

I found that duration keep increasing while Hue session is opened.

So I guess that 'Duration' is not a exact execution time..

Is it bug?

Translate
EricL
Platinum ⭐️⭐️
EricLAnswer
Platinum ⭐️⭐️
June 19, 2019
Hi @Mogiking

Hue keeps the query handler open so that it can get back to its result during pagination. This is a feature in Hue, not a bug.

You can find that info from impala PROFILE under Query Timeline section, like below:

Query Timeline
Query submitted: 0ns (0)
Planning finished: 170ms (170000854)
Submit for admission: 172ms (172000864)
Completed admission: 172ms (172000864)
Ready to start on 2 backends: 172ms (172000864)
All 2 execution backends (3 fragment instances) started: 176ms (176000884)
Rows available: 422ms (422002119)
First row fetched: 501ms (501002515)
Unregister query: 509ms (509002555)

You can see detailed information on when data is available.

Cheers
Eric
Translate