You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Venkat Atmuri (JIRA)" <ji...@apache.org> on 2018/03/08 19:32:00 UTC

[jira] [Closed] (IMPALA-6091) Impala Queries Executing long time (long running impala queries)

     [ https://issues.apache.org/jira/browse/IMPALA-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Venkat Atmuri closed IMPALA-6091.
---------------------------------

> Impala Queries Executing long time (long running impala queries)
> ----------------------------------------------------------------
>
>                 Key: IMPALA-6091
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6091
>             Project: IMPALA
>          Issue Type: Bug
>         Environment: Impala Shell v2.7.0-cdh5.10.1
>            Reporter: Venkat Atmuri
>            Priority: Major
>         Attachments: impala executing time.PNG
>
>
> 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.
>  
> https://www.cloudera.com/documentation/enterprise/latest/topics/impala_query_timeout_s.html
>  
> It seems like it’s almost necessary to run two instances of Impala (one for Tableau and one for all other requests).
>  
> Any suggestions?
>  
>  
>  
> Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)