[ 
https://issues.apache.org/jira/browse/IMPALA-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169402#comment-17169402
 ] 

Tim Armstrong commented on IMPALA-10036:
----------------------------------------

Hmm, it seems to think there are multiple coordinator fragments.

{noformat}
I0801 13:14:56.301012 31596 scheduler.cc:279] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for coordinator 
fragment F16
I0801 13:14:56.301020 31596 scheduler.cc:310] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for interior fragment.
I0801 13:14:56.301028 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.301044 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.302242 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.302261 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.302278 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.303480 31596 scheduler.cc:310] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for interior fragment.
I0801 13:14:56.303490 31596 scheduler.cc:279] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for coordinator 
fragment F25
I0801 13:14:56.303498 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.303514 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.303537 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.303556 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.303573 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.303589 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.304808 31596 scheduler.cc:310] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for interior fragment.
I0801 13:14:56.304818 31596 scheduler.cc:310] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for interior fragment.
I0801 13:14:56.304826 31596 scheduler.cc:310] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for interior fragment.
I0801 13:14:56.304832 31596 scheduler.cc:305] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for scan and/or union 
fragment.
I0801 13:14:56.304850 31596 scheduler.cc:279] 
b944ca1e1c374c6f:5ad64c6100000000] Computing exec params for coordinator 
fragment F37
{noformat}

> Admission control incorrectly rejecting query based on coordinator limit
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-10036
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10036
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 4.0
>            Reporter: David Rorke
>            Assignee: Tim Armstrong
>            Priority: Major
>         Attachments: 23_profile.txt, backends-repro.png, impalad.INFO.gz, 
> start-ded-coord-cluster.sh, tmp-fair-scheduler.xml, tmp-llama-site.xml
>
>
> Admission control rejected a query with the following error:
> {noformat}
> ERROR: Rejected query from pool root.default: request memory needed 50.00 GB 
> is greater than memory available for admission 45.36 GB of 
> coordinator-0:22050.
> {noformat}
> The query profile shows the following resource estimates:
> {noformat}
> Per-Host Resource Estimates: Memory=303.36GB
> Dedicated Coordinator Resource Estimate: Memory=136MB
> {noformat}
> The max query memory limit for the pool was configured as 50 GB.
> Based on the coordinator resource estimate of 136 MB the query should have 
> easily fit in the available coordinator memory. [~tarmstrong] speculated that 
> we might simply be comparing the wrong resource estimate to the coordinator 
> limit.
> Profile attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to