You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/02/19 20:13:00 UTC
[jira] [Created] (IMPALA-8222) Timeout calculation in stress test
doesn't make sense
Tim Armstrong created IMPALA-8222:
-------------------------------------
Summary: 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
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.
* 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 revisiting it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)