ASF GitHub Bot commented on YARN-2162:

GitHub user flyrain reopened a pull request:


    YARN-2162. add ability to optionally configure maxResources in terms …

    …of percentage

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/flyrain/hadoop yarn-2162

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #261
commit bd8f446eaa17a35d1b50e6206f82374ca1600125
Author: Yufei Gu <yufei@...>
Date:   2017-09-22T02:20:37Z


commit 977b6eab736d08639c0b3e624b041521181346dd
Author: Yufei Gu <yufei@...>
Date:   2017-09-25T17:35:23Z

    YARN-2162 fixed style issues

commit c68fe76adc0f48791a369a49119c88adf3d10c8d
Author: Yufei Gu <yufei@...>
Date:   2017-09-28T18:28:52Z


commit 65ce5f14dd2d8f8560e2b7389ee830c225a2df25
Author: Yufei Gu <yufei@...>
Date:   2017-10-05T17:06:40Z



> add ability in Fair Scheduler to optionally configure maxResources in terms 
> of percentage
> -----------------------------------------------------------------------------------------
>                 Key: YARN-2162
>                 URL: https://issues.apache.org/jira/browse/YARN-2162
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler, scheduler
>            Reporter: Ashwin Shankar
>            Assignee: Yufei Gu
>            Priority: Major
>              Labels: scheduler
>             Fix For: 2.9.0, 3.0.0, 3.1.0
>         Attachments: YARN-2162.001.patch, YARN-2162.002.patch, 
> YARN-2162.003.patch, YARN-2162.004.patch, YARN-2162.005.patch, 
> YARN-2162.006.patch, YARN-2162.007.patch, YARN-2162.008.patch, 
> YARN-2162.branch-2.010.patch, YARN-2162.branch-3.0.009.patch, 
> test-400nm-200app-2k_NODE_UPDATE.timecost.svg
> minResources and maxResources in fair scheduler configs are expressed in 
> terms of absolute numbers X mb, Y vcores. 
> As a result, when we expand or shrink our hadoop cluster, we need to 
> recalculate and change minResources/maxResources accordingly, which is pretty 
> inconvenient.
> We can circumvent this problem if we can optionally configure these 
> properties in terms of percentage of cluster capacity. 

This message was sent by Atlassian JIRA

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

Reply via email to