[ https://issues.apache.org/jira/browse/IMPALA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693795#comment-16693795 ]
Michael Ho commented on IMPALA-539: ----------------------------------- Given that we probably need a timeout for response of the cancellation RPC issued by the coordinator, we probably need to think through what the relationship it may have with IMPALA-2990. In IMPALA-2990, a query will be cancelled if a particular backend hasn't reported any status for a certain timeout period. If fixing this Jira means waiting for backends to reply during cancellation, this may lengthen the overall timeout of hung queries due to unresponsive backends. > Impala should gather final runtime profile from fragments for > aborted/cancelled query > ------------------------------------------------------------------------------------- > > Key: IMPALA-539 > URL: https://issues.apache.org/jira/browse/IMPALA-539 > Project: IMPALA > Issue Type: Improvement > Components: Backend > Affects Versions: Impala 1.1 > Reporter: Alan Choi > Priority: Minor > Labels: query-lifecycle > > For cancelled/aborted queries, the final runtime profile from plan fragments > are not recorded and reported by the coordinator. For short running queries, > we won't see any profile at all because no intermediate runtime profile has > been sent. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org