You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/04/30 19:08:00 UTC
[jira] [Work started] (IMPALA-6984) Coordinator should cancel
backends when returning EOS
[ https://issues.apache.org/jira/browse/IMPALA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on IMPALA-6984 started by Tim Armstrong.
---------------------------------------------
> Coordinator should cancel backends when returning EOS
> -----------------------------------------------------
>
> Key: IMPALA-6984
> URL: https://issues.apache.org/jira/browse/IMPALA-6984
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Affects Versions: Impala 3.0
> Reporter: Daniel Hecht
> Assignee: Tim Armstrong
> Priority: Major
> Labels: query-lifecycle
>
> Currently, the Coordinator waits for backends rather than proactively cancelling them in the case of hitting EOS. There's a tangled mess that makes it tricky to proactively cancel the backends related to how {{Coordinator::ComputeQuerySummary()}} works – we can't update the summary until the profiles are no longer changing (which also makes sense given that we want the exec summary to be consistent with the final profile). But we current tie together the FIS status and the profile, and cancellation of backends causes the FIS to return CANCELLED, which then means that the remaining FIS on that backend won't produce a final profile.
> With the rework of the protocol for IMPALA-2990 we should make it possible to sort this out such that a final profile can be requested regardless of how a FIS ends execution.
> This also relates to IMPALA-5783.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org