[
https://issues.apache.org/jira/browse/IMPALA-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169420#comment-17169420
]
Tim Armstrong commented on IMPALA-10036:
----------------------------------------
Talked with [~bikram.sngh91] and this was the intended behaviour for
non-coordinator fragments that get scheduled in the coordinator, but I don't
think we realised the consequences. We think it would make sense to schedule
these fragments on an executor instead.
> 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]
