I'm seeing a lot of simple queries like, “SELECT * FROM DATABASE.TABLE”, “SHOW TABLES” and “DESCRIBE database.table” that hang around in the list and say they’re Executing, even 90-170 minutes after they’ve completed.
I would like to know if there is a way to configure Impala to stop/cancel a long-running query after a certain amount of time.
Found the below link to set time limit but were using TABLEAU so need more time for tableau(6 users) queries.
It seems like it’s almost necessary to run two instances of Impala (one for Tableau and one for all other requests).
That can be seen in "query detail" : query timeline
For queries already completed there should be a row for first row fetched.
I'm not aware of any option to see it on impala queries page.
You can also set idle query timeout and idle session timeout in impala advance snippet to force timeout for queries running from hue.
We are also seeing a problem when query run from Hue query gets completed but when we see the running queries in Impala cloudera Manager, we see its in executing state.
Can you please help us understand what could be the reason.