Details
-
Sub-task
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
Impala 3.0
-
None
-
ghx-label-5
Description
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.
Attachments
Issue Links
- causes
-
IMPALA-9755 Flaky test: test_global_exchange_counters
- Resolved
- depends upon
-
IMPALA-5119 Don't make RPCs from Coordinator::UpdateBackendExecStatus()
- Open
- is related to
-
IMPALA-2990 Coordinator should timeout and cancel queries with unresponsive / stuck executors
- Resolved
-
IMPALA-5783 Investigate exec summary behavior
- Resolved
-
IMPALA-539 Impala should gather final runtime profile from fragments for aborted/cancelled query
- Resolved
- relates to
-
IMPALA-5119 Don't make RPCs from Coordinator::UpdateBackendExecStatus()
- Open
-
IMPALA-8845 Close ExecNode tree prior to calling FlushFinal in FragmentInstanceState
- Resolved
-
IMPALA-9113 Queries can hang if an impalad is killed after a query has FINISHED
- Resolved
-
IMPALA-9124 Transparently retry queries that fail due to cluster membership changes
- In Progress
-
IMPALA-3990 ExchangeNode::Close() cancel sender fragment if called before eos
- Open