[
https://issues.apache.org/jira/browse/IMPALA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-2205.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
IMPALA-9611 added a check for any non-cancelled fragments in test_failpoints. I
think this achieves what this JIRA is talking about.
> Make cancellation tests check whether all fragments finish
> ----------------------------------------------------------
>
> Key: IMPALA-2205
> URL: https://issues.apache.org/jira/browse/IMPALA-2205
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 2.3.0
> Reporter: Henry Robinson
> Assignee: Henry Robinson
> Priority: Minor
> Labels: test-infra
> Fix For: Impala 4.0
>
>
> To test some of the changes for IMPALA-1599, it would be good to test the
> following case:
> A query runs. One fragment is delayed at the start of {{Prepare()}}. A
> cancellation request comes in . Does the fragment eventually get cancelled?
> Is that true for the coordinator as well?
> We can do this with debug actions, but we need to make the tests check if
> there are any fragments left in flight after cancellation has finished and
> the node has had time to quiesce. IMPALA-1599 will introduce a metric that we
> can check to see how many fragments are still running.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
