[
https://issues.apache.org/jira/browse/IMPALA-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikramjeet Vig resolved IMPALA-8830.
------------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Coordinator-only queries get queued when there are no executor groups
> ---------------------------------------------------------------------
>
> Key: IMPALA-8830
> URL: https://issues.apache.org/jira/browse/IMPALA-8830
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.3.0
> Reporter: Tim Armstrong
> Assignee: Bikramjeet Vig
> Priority: Blocker
> Labels: admission-control, resource-management
> Fix For: Impala 4.0
>
>
> Reproduction:
> {noformat}
> tarmstrong@tarmstrong-box:~/Impala/incubator-impala$ start-impala-cluster.py
> -s1 --use_exclusive_coordinators;
> [localhost:21000] default> select * from tpch.lineitem order by l_orderkey
> limit 5;
> ERROR: Admission for query exceeded timeout 60000ms in pool default-pool.
> Queued reason: No healthy executor groups found for pool default-pool.
> [localhost:21000] default> select 1;
> ERROR: Admission for query exceeded timeout 60000ms in pool default-pool.
> Queued reason: No healthy executor groups found for pool default-pool.
> {noformat}
> I expected that the second query should run immediately since it doesn't
> actually need to be scheduled on any executors. I suspect this may be a
> regression from the executor group changes, but didn't confirm.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
