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 "Michael Brown (JIRA)" <ji...@apache.org> on 2018/10/22 20:14:00 UTC
[jira] [Commented] (IMPALA-7736) stress: AssertionError: The number
of executing queries is negative
[ https://issues.apache.org/jira/browse/IMPALA-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659627#comment-16659627 ]
Michael Brown commented on IMPALA-7736:
---------------------------------------
So I did some combing to find where else this may have happened, it and it all hits on 2.12-based, not 3.1-based builds, with the stress test executed on master.
The assert is always this second one:
{noformat}
@property
def _num_queries_active(self):
"""The number of queries that are currently active (i.e. submitted to a query runner
and haven't yet completed)."""
num_running = self._num_queries_submitted.value - self._num_queries_finished.value
assert num_running >= 0, "The number of running queries is negative"
return num_running
@property
def _num_queries_executing(self):
"""The number of queries that are currently executing (i.e. entered the RUNNING state
and haven't yet completed)."""
num_executing = (self._num_queries_started_running_or_cancelled.value -
self._num_queries_finished.value)
assert num_executing >= 0, "The number of executing queries is negative"
return num_executing
{noformat}
I..e, it's the {{num_executing}} assert.
> stress: AssertionError: The number of executing queries is negative
> -------------------------------------------------------------------
>
> Key: IMPALA-7736
> URL: https://issues.apache.org/jira/browse/IMPALA-7736
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.1.0
> Reporter: Michael Brown
> Priority: Critical
> Labels: stress
>
> I'd heard about this anecdotally but haven't seen it until now:
> {noformat}
> Done | Active | Executing | Mem Lmt Ex | AC Reject | AC Timeout | Time Out | Cancel | Err | Incorrect | Next Qry Mem Lmt | Tot Qry Mem Lmt | Tracked Mem | RSS Mem
> 263 | 6 | 3 | 20 | 0 | 0 | 0 | 17 | 0 | 0 | 9818 | 26802 | 15656 | 19329
> 263 | 6 | 3 | 20 | 0 | 0 | 0 | 17 | 0 | 0 | 9818 | 26802 | 15534 | 19341
> 263 | 6 | 3 | 20 | 0 | 0 | 0 | 17 | 0 | 0 | 9818 | 26802 | 15462 | 19190
> 265 | 4 | 1 | 20 | 0 | 0 | 0 | 17 | 0 | 0 | 9818 | 22938 | 15482 | 19565
> Traceback (most recent call last):
> File "tests/stress/concurrent_select.py", line 2320, in <module>
> main()
> File "tests/stress/concurrent_select.py", line 2316, in main
> select_probability=args.select_probability)
> File "tests/stress/concurrent_select.py", line 529, in run_queries
> self._wait_for_test_to_finish(impala, should_print_status)
> File "tests/stress/concurrent_select.py", line 943, in _wait_for_test_to_finish
> self._print_status(print_header=(lines_printed == 0))
> File "tests/stress/concurrent_select.py", line 837, in _print_status
> self._num_queries_executing,
> File "tests/stress/concurrent_select.py", line 690, in _num_queries_executing
> assert num_executing >= 0, "The number of executing queries is negative"
> AssertionError: The number of executing queries is negative
> {noformat}
> I've run many thousand-query stress test runs against 3.1 without hitting this. Where this finally happened was against a 2.12-based build, if that matters.
--
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