[
https://issues.apache.org/jira/browse/IMPALA-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498304#comment-16498304
]
Thomas Tauber-Marshall commented on IMPALA-6956:
------------------------------------------------
Saw this again. [~vukercegovac] can you take a look at this. I think you
touched this test most recently, in IMPALA-6602. Thanks
> check_num_executing fails test_query_expiration
> -----------------------------------------------
>
> Key: IMPALA-6956
> URL: https://issues.apache.org/jira/browse/IMPALA-6956
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Vuk Ercegovac
> Priority: Blocker
>
> This happened recently on an s3 build. The check that asserts the number of
> currently running queries comes back a few queries short.
> {noformat}
> custom_cluster/test_query_expiration.py:71: in test_query_expiration
> self._check_num_executing(impalad, len(handles))
> custom_cluster/test_query_expiration.py:38: in _check_num_executing assert
> actual == expected
> E assert 2 == 4
> {noformat}
> The last query is executed with:
> {noformat}
> I0426 01:57:29.507251 12229 query-state.cc:395] Executing instance.
> instance_id=be4bd338f1d8a8ef:651e7a3c00000000 fragment_idx=0
> per_fragment_instance_idx=0 coord_state_idx=0 #in-flight=4
> {noformat}
> So there are 4 in flight at that time. However, prior to this, I see that
> some are in the process of being cancelled:
> {noformat}
> I0426 01:57:29.022300 11843 impala-server.cc:1908] Expiring query
> 524c239e0d9f6356:b70c252400000000 due to execution time limit of 1s.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
