You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/07/30 21:41:49 UTC

[jira] [Commented] (AMBARI-2765) Hadoop2: Capacity Scheduler changes not being persisted in capacity-scheduler.xml

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

Sumit Mohanty commented on AMBARI-2765:
---------------------------------------

LGTM, +1.
                
> Hadoop2: Capacity Scheduler changes not being persisted in capacity-scheduler.xml
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-2765
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2765
>             Project: Ambari
>          Issue Type: Task
>          Components: agent
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 1.4.0
>
>         Attachments: AMBARI-2765.patch
>
>
> From UI, changed/save the following properties in capacity scheduler. Once service was started, capacity-scheduler.xml still had the old values.
> * "yarn.scheduler.capacity.maximum-applications" : "10111"
> * "yarn.scheduler.capacity.root.capacity" : "111"

--
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