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 "Szilard Nemeth (JIRA)" <ji...@apache.org> on 2018/07/27 09:04:00 UTC

[jira] [Commented] (YARN-7948) Enable refreshing maximum allocation for multiple resource types

    [ https://issues.apache.org/jira/browse/YARN-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559440#comment-16559440 ] 

Szilard Nemeth commented on YARN-7948:
--------------------------------------

First patch uploaded. Added one testcase that specifically checks that a maximum allocation value of a custom resource refreshed when FS.reinit() is called.
[~rkanter], [~haibochen]: Can you think of any more tests that would be useful?
Thanks! 

> Enable refreshing maximum allocation for multiple resource types
> ----------------------------------------------------------------
>
>                 Key: YARN-7948
>                 URL: https://issues.apache.org/jira/browse/YARN-7948
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>    Affects Versions: 3.0.0
>            Reporter: Yufei Gu
>            Assignee: Szilard Nemeth
>            Priority: Major
>         Attachments: YARN-7948.001.patch
>
>
> YARN-7738 did the same thing for CS. We need a fix for FS. We could fix it by moving the refresh code from class CS to class AbstractYARNScheduler. 



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

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