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 "Thomas Graves (JIRA)" <ji...@apache.org> on 2013/04/02 14:25:15 UTC

[jira] [Updated] (YARN-525) make CS node-locality-delay refreshable

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

Thomas Graves updated YARN-525:
-------------------------------

    Issue Type: Improvement  (was: Bug)
       Summary: make CS node-locality-delay refreshable  (was: yarn.scheduler.capacity.node-locality-delay doesn't change with rmadmin -refreshQueues)
    
> make CS node-locality-delay refreshable
> ---------------------------------------
>
>                 Key: YARN-525
>                 URL: https://issues.apache.org/jira/browse/YARN-525
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>    Affects Versions: 2.0.3-alpha, 0.23.7
>            Reporter: Thomas Graves
>
> the config yarn.scheduler.capacity.node-locality-delay doesn't change when you change the value in capacity_scheduler.xml and then run yarn rmadmin -refreshQueues.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira