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 2018/10/02 01:12:00 UTC

[jira] [Updated] (IMPALA-1226) need better cancellation tests

     [ https://issues.apache.org/jira/browse/IMPALA-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong updated IMPALA-1226:
----------------------------------
    Priority: Major  (was: Critical)

> need better cancellation tests
> ------------------------------
>
>                 Key: IMPALA-1226
>                 URL: https://issues.apache.org/jira/browse/IMPALA-1226
>             Project: IMPALA
>          Issue Type: Task
>          Components: Infrastructure
>    Affects Versions: Impala 2.0
>            Reporter: Dan Hecht
>            Assignee: Dan Hecht
>            Priority: Major
>              Labels: query-lifecycle, test, test-infra
>         Attachments: impala-1178-test.patch
>
>
> See IMPALA-1178 comments for details for how to manually reproduce the bug.
> I tried writing a pytest test case to reproduce the problem but it appears that we don't get enough parallelism that way.  Even adding a long delay loop to ImpalaServer::ExecuteStatement inside the race window shows that the attached test will not execute the RPCs concurrently, and so doesn't reproduce IMPALA-1178.
> I'll attach a patch of the test case attempt.  The patch also contains some instrumentation I was using to see why I wasn't hitting the race window.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org