[
https://issues.apache.org/jira/browse/IMPALA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699646#comment-16699646
]
Tim Armstrong commented on IMPALA-6194:
---------------------------------------
[~lv][~kwho] is there anything concrete to do here except for IMPALA-7738?
Preventing I/O threads from getting stuck seems to be the key thing here so
long as we're sticking with the current polling-based cancellation scheme. Or
do we want to keep this open to track the general problem.
> Ensure all fragment instances notice cancellation
> -------------------------------------------------
>
> Key: IMPALA-6194
> URL: https://issues.apache.org/jira/browse/IMPALA-6194
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Lars Volker
> Priority: Critical
> Labels: observability, supportability
>
> Currently queries can get stuck in an uncancellable state, e.g. when blocking
> on function calls or condition variables without periodically checking for
> cancellation. We should eliminate all those calls and make sure we don't
> re-introduce such issues. One option would be a watchdog to check that each
> fragment instance regularly calls RETURN_IF_CANCEL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
