[
https://issues.apache.org/jira/browse/YARN-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372526#comment-16372526
]
Wangda Tan commented on YARN-7738:
----------------------------------
[~yufeigu], CS support refresh maximum allocation while RM is running, and the
new_max_alloc must >= old_max_alloc.
The patch fixed an issue that resource-types.xml isn't loaded during the
refresh. This causes after refresh, all maximum-allocation for non-memory/vcore
resource becomes 0
> CapacityScheduler: Support refresh maximum allocation for multiple resource
> types
> ---------------------------------------------------------------------------------
>
> Key: YARN-7738
> URL: https://issues.apache.org/jira/browse/YARN-7738
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Sumana Sathish
> Assignee: Wangda Tan
> Priority: Blocker
> Fix For: 3.1.0
>
> Attachments: YARN-7738.001.patch, YARN-7738.002.patch,
> YARN-7738.003.patch, YARN-7738.004.patch
>
>
> Currently CapacityScheduler fails to refresh maximum allocation for multiple
> resource types.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
