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 "David Rorke (Jira)" <ji...@apache.org> on 2020/08/01 01:11:00 UTC
[jira] [Updated] (IMPALA-10036) Admission control incorrectly
rejecting query based on coordinator limit
[ https://issues.apache.org/jira/browse/IMPALA-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Rorke updated IMPALA-10036:
---------------------------------
Attachment: 23_profile.txt
> 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
> Priority: Major
> Attachments: 23_profile.txt
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org