[ 
https://issues.apache.org/jira/browse/IMPALA-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Buss updated IMPALA-8469:
-----------------------------
    Description: 
When configuring admission control with dedicated coordinator daemons, queries 
in pools with memory limits fail with the admission rejections like the 
following:
{noformat}
Rejected query from pool root.default: request memory needed 3.00 GB per node 
is greater than memory available for admission 0 of coord1.example.com:22000. 
Use the MEM_LIMIT query option to indicate how much memory is required per 
node.{noformat}
Tracing this in the code leads us to line 576 of {{admission-controller.cc}} 
and therefore to suspect that the local {{TBackendDescriptor}} 
({{local_backend_descriptor_}}) for the coordinator node in {{scheduler.cc}} 
never has {{admit_mem_limit}} set, and thus ends up with the default value of 0.

The issue goes away if NO_SPECIALIZATION is used instead of COORDINATOR_ONLY.

  was:
When configuring admission control with dedicated coordinator daemons, queries 
with pool memory limits fail with the admission rejections like the following:
{noformat}
Rejected query from pool root.default: request memory needed 3.00 GB per node 
is greater than memory available for admission 0 of coord1.example.com:22000. 
Use the MEM_LIMIT query option to indicate how much memory is required per 
node.{noformat}
Tracing this in the code leads us to line 576 of {{admission-controller.cc}} 
and therefore to suspect that the local {{TBackendDescriptor}} 
({{local_backend_descriptor_}}) for the coordinator node in {{scheduler.cc}} 
never has {{admit_mem_limit}} set, and thus ends up with the default value of 0.

The issue goes away if NO_SPECIALIZATION is used instead of COORDINATOR_ONLY.


> Admit memory not set in backend descriptor for coordinator-only nodes
> ---------------------------------------------------------------------
>
>                 Key: IMPALA-8469
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8469
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 3.2.0
>            Reporter: Ian Buss
>            Priority: Critical
>              Labels: admission-control, resource-management
>
> When configuring admission control with dedicated coordinator daemons, 
> queries in pools with memory limits fail with the admission rejections like 
> the following:
> {noformat}
> Rejected query from pool root.default: request memory needed 3.00 GB per node 
> is greater than memory available for admission 0 of coord1.example.com:22000. 
> Use the MEM_LIMIT query option to indicate how much memory is required per 
> node.{noformat}
> Tracing this in the code leads us to line 576 of {{admission-controller.cc}} 
> and therefore to suspect that the local {{TBackendDescriptor}} 
> ({{local_backend_descriptor_}}) for the coordinator node in {{scheduler.cc}} 
> never has {{admit_mem_limit}} set, and thus ends up with the default value of 
> 0.
> The issue goes away if NO_SPECIALIZATION is used instead of COORDINATOR_ONLY.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to