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 "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/08/03 21:25:00 UTC

[jira] [Created] (IMPALA-8830) Coordinator-only queries get queued when there are no executor groups

Tim Armstrong created IMPALA-8830:
-------------------------------------

             Summary: 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
            Reporter: Tim Armstrong
            Assignee: Bikramjeet Vig


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
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org