[jira] [Resolved] (IMPALA-8222) Timeout calculation in stress test doesn't make sense

["Tim Armstrong (JIRA)" <ji...@apache.org>]

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

Tim Armstrong resolved IMPALA-8222.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.2.0

> Timeout calculation in stress test doesn't make sense
> -----------------------------------------------------
>
>                 Key: IMPALA-8222
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8222
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>             Fix For: Impala 3.2.0
>
>
> There is some logic in the stress test that tries to guess what a reasonable timeout for a query is. There are enough fudge factors that the false positive rate is fairly low, but it also doesn't provide much useful coverage unless a query is stuck. But an overall job timeout achieves the same thing.
> Some specific issues that the current logic has (and which are tricky to solve):
> * The number of concurrent queries is calculated at query submission time. E.g. a query that starts before a large batch of other queries is submitted will be given a short timeout multiplier.
> * There is no guarantee that performance degrades linearly. E.g. if runtime filters arrive late, we can see much larger perf hits.
> We should consider removing the timeout enforcement or at least revisit it.



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