You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "liu bin (Jira)" <ji...@apache.org> on 2022/07/04 09:40:00 UTC

[jira] [Updated] (YARN-11205) Do not reset max applications for a queue based on absolute capacity

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

liu bin updated YARN-11205:
---------------------------
    Description: 
when we use absolute resource configuration in capacityscheduler, the max applications will be reset based on queue‘s AbsoluteCapacity.

When the cluster is just started and nodemanager has not been registered, max applications will be set to 0, applications cannot be submitted.

RM log:
{code:java}
LeafQueue:root.hadoop, maxApplications=0, maxApplicationsPerUser=0, Abs Cap:NaN{code}

I think  it's meaningless to reset max applications, so we can just delete these codes.

  was:
when we use absolute resource configuration in capacityscheduler, the max applications will be reset based on queue‘s AbsoluteCapacity.

When the cluster is just started and nodemanager has not been registered, max applications will be set to 0, applications cannot be submitted.

RM log:
LeafQueue:root.hadoop, maxApplications=0, maxApplicationsPerUser=0, Abs Cap:NaN
I think  it's meaningless to reset max applications, so we can just delete these codes.


> Do not reset max applications for a queue based on absolute capacity
> --------------------------------------------------------------------
>
>                 Key: YARN-11205
>                 URL: https://issues.apache.org/jira/browse/YARN-11205
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>            Reporter: liu bin
>            Priority: Major
>              Labels: capacityscheduler
>
> when we use absolute resource configuration in capacityscheduler, the max applications will be reset based on queue‘s AbsoluteCapacity.
> When the cluster is just started and nodemanager has not been registered, max applications will be set to 0, applications cannot be submitted.
> RM log:
> {code:java}
> LeafQueue:root.hadoop, maxApplications=0, maxApplicationsPerUser=0, Abs Cap:NaN{code}
> I think  it's meaningless to reset max applications, so we can just delete these codes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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