[ https://issues.apache.org/jira/browse/IMPALA-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-3867. ----------------------------------- Resolution: Later > tool to kill runaway queries > ---------------------------- > > Key: IMPALA-3867 > URL: https://issues.apache.org/jira/browse/IMPALA-3867 > Project: IMPALA > Issue Type: New Feature > Components: Clients > Affects Versions: Impala 2.5.0 > Reporter: Marcell Szabo > Priority: Minor > > We already have a [good > mechanism|http://www.cloudera.com/documentation/enterprise/latest/topics/impala_timeouts.html#timeouts__impalad_timeout] > for killing idle queries. > In some situations it would be nice to have a tool that kills active queries > based on configurable rules, e.g. runtime or memory consumed goes over a > limit. > A first approach could be a script using CM API calls impalaQueries and > impalaQueries/cancel. > It would be nice though if the user who originally started the query would > see a custom error message that describes why and who killed the query. This > should also be stored in the profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005)