ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-6269) Capacity Scheduler config default in Ambari should not have unfunded queue config
Date Thu, 10 Jul 2014 00:10:05 GMT

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

Yusaku Sako updated AMBARI-6269:
--------------------------------

    Assignee: Jayush Luniya

> Capacity Scheduler config default in Ambari should not have unfunded queue config
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-6269
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6269
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>              Labels: patch
>             Fix For: 1.7.0
>
>         Attachments: Ambari-6269.patch
>
>
> This is the default config in Ambari deployed clusters. We should remove the line 'yarn.scheduler.capacity.root.unfunded.capacity=50'.
> yarn.scheduler.capacity.maximum-am-resource-percent=0.2
> yarn.scheduler.capacity.maximum-applications=10000
> yarn.scheduler.capacity.node-locality-delay=40
> yarn.scheduler.capacity.root.acl_administer_queues=*
> yarn.scheduler.capacity.root.capacity=100
> yarn.scheduler.capacity.root.default.acl_administer_jobs=*
> yarn.scheduler.capacity.root.default.acl_submit_jobs=*
> yarn.scheduler.capacity.root.default.capacity=100
> yarn.scheduler.capacity.root.default.maximum-capacity=100
> yarn.scheduler.capacity.root.default.state=RUNNING
> yarn.scheduler.capacity.root.default.user-limit-factor=1
> yarn.scheduler.capacity.root.queues=default
> yarn.scheduler.capacity.root.unfunded.capacity=50



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

Mime
View raw message