You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Rémy SAISSY (JIRA)" <ji...@apache.org> on 2014/03/11 18:35:46 UTC

[jira] [Created] (AMBARI-5032) YARN Scheduler section drop lines when saving a scheduler configuration

Rémy SAISSY created AMBARI-5032:
-----------------------------------

             Summary: YARN Scheduler section drop lines when saving a scheduler configuration
                 Key: AMBARI-5032
                 URL: https://issues.apache.org/jira/browse/AMBARI-5032
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 1.4.1
            Reporter: Rémy SAISSY


Hi,
in Ambari, Services:YARN::config::Scheduler, when I copy paste the following configuration:

yarn.scheduler.capacity.maximum-am-resource-percent=0.2
yarn.scheduler.capacity.maximum-applications=10000
yarn.scheduler.capacity.root.capacity=100
yarn.scheduler.capacity.root.queues=default,datalab,batch,restit
yarn.scheduler.capacity.root.default.capacity=5
yarn.scheduler.capacity.root.default.maximum-capacity=5
yarn.scheduler.capacity.root.default.state=RUNNING
yarn.scheduler.capacity.root.default.acl_administer_queue= users
yarn.scheduler.capacity.root.datalab.capacity=10
yarn.scheduler.capacity.root.datalab.maximum-capacity=10
yarn.scheduler.capacity.root.datalab.state=RUNNING
yarn.scheduler.capacity.root.datalab.acl_submit_applications= datalab_users
yarn.scheduler.capacity.root.datalab.acl_administer_queue= datalab_admins
yarn.scheduler.capacity.root.batch.capacity=40
yarn.scheduler.capacity.root.batch.maximum-capacity=40
yarn.scheduler.capacity.root.batch.state=RUNNING
yarn.scheduler.capacity.root.batch.acl_submit_applications= batch_users
yarn.scheduler.capacity.root.batch.acl_administer_queue= batch_admins
yarn.scheduler.capacity.root.default.capacity=45
yarn.scheduler.capacity.root.default.maximum-capacity=45
yarn.scheduler.capacity.root.default.state=RUNNING
yarn.scheduler.capacity.root.default.acl_submit_applications= restit_users
yarn.scheduler.capacity.root.default.acl_administer_queue= restit_admins

and click Save, Ambari saves the following invalid configuration:

yarn.scheduler.capacity.maximum-am-resource-percent=0.2
yarn.scheduler.capacity.maximum-applications=10000
yarn.scheduler.capacity.root.batch.capacity=40
yarn.scheduler.capacity.root.batch.maximum-capacity=40
yarn.scheduler.capacity.root.batch.state=RUNNING
yarn.scheduler.capacity.root.capacity=100
yarn.scheduler.capacity.root.datalab.capacity=10
yarn.scheduler.capacity.root.datalab.maximum-capacity=10
yarn.scheduler.capacity.root.datalab.state=RUNNING
yarn.scheduler.capacity.root.default.capacity=45
yarn.scheduler.capacity.root.default.maximum-capacity=45
yarn.scheduler.capacity.root.default.state=RUNNING
yarn.scheduler.capacity.root.queues=default,datalab,batch,restit

And the ResourceManager doesn't restart properly due to a Capacity Scheduler configuration file issue.




--
This message was sent by Atlassian JIRA
(v6.2#6252)