Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Impala Queries

avatar
Rising Star

Hello,

We are seeing a few Impala queries running for more than 3 hours in Impala. Upon checking we found that the query is in exception state however on the Cloudera Impala GUI it still showing it as running. Would like to know if there is a way to kill such type of queries at Impala level.

We have implemented Impala ACL and set the Queue Timeout to 5 minutes yet some queries keep running. Our applications connect to Impala via JDBC and we also have some users who use Hue to run queries.

 

Any assistance/guidance is much appreciated.

 

1 ACCEPTED SOLUTION

avatar
Expert Contributor

Hello,

 

There is no such way to kill the query in one go.

 

You need to either do it by one of the following methods:-

 

You can kill the query from the Impala Daemon web UI of the Impala
Daemon coordinating the query. 

or 

you can try killing from the browser.

https://<query_coordinator_server_name>:25000/close_session?session_id=<session_id>

View solution in original post

3 REPLIES 3

avatar
Expert Contributor

Hello,

 

You can kill the query from the Impala Daemon web UI of the Impala
Daemon coordinating the query. 

 

or 

 

you can try killing from the browser.

 

https://<query_coordinator_server_name>:25000/close_session?session_id=<session_id>

 

Please let us know if it helps

avatar
Rising Star

Hi @ShankerSharma 

I am currently killing the query from Impala GUI, however, this becomes overkill when there are many queries in a state of exception. Was wondering if there could be a faster way to select all of such queries and kill them in one go.

 

 

avatar
Expert Contributor

Hello,

 

There is no such way to kill the query in one go.

 

You need to either do it by one of the following methods:-

 

You can kill the query from the Impala Daemon web UI of the Impala
Daemon coordinating the query. 

or 

you can try killing from the browser.

https://<query_coordinator_server_name>:25000/close_session?session_id=<session_id>