You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Swapan Shridhar (JIRA)" <ji...@apache.org> on 2016/05/27 01:13:12 UTC
[jira] [Updated] (AMBARI-16919) Handle the scenario when
'capacity-scheduler' is passed-in as dictionary to Stack Advisor and
services['configurations']["capacity-scheduler"]["properties"]["capacity-scheduler"]
is null.
[ https://issues.apache.org/jira/browse/AMBARI-16919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapan Shridhar updated AMBARI-16919:
-------------------------------------
Description:
AMBARI-16888 handled the scenario when capacity-scheduler is passed in as dictionary and
{code}
"capacity-scheduler" : {
"properties" : {
"capacity-scheduler" : "null",
"yarn.scheduler.capacity.root.accessible-node-labels" : "*",
"yarn.scheduler.capacity.maximum-am-resource-percent" : "1",
"yarn.scheduler.capacity.root.acl_administer_queue" : "*",
"yarn.scheduler.capacity.queue-mappings-override.enable" : 'false',
"yarn.scheduler.capacity.root.default.capacity" : "100",
"yarn.scheduler.capacity.root.default.user-limit-factor" : "1",
"yarn.scheduler.capacity.root.queues" : "default",
"yarn.scheduler.capacity.root.capacity" : "100",
"yarn.scheduler.capacity.root.default.acl_submit_applications" : "*",
"yarn.scheduler.capacity.root.default.maximum-capacity" : "100",
"yarn.scheduler.capacity.node-locality-delay" : "40",
"yarn.scheduler.capacity.maximum-applications" : "10000",
"yarn.scheduler.capacity.root.default.state" : "RUNNING"
}
},
{code}
> Handle the scenario when 'capacity-scheduler' is passed-in as dictionary to Stack Advisor and services['configurations']["capacity-scheduler"]["properties"]["capacity-scheduler"] is null.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16919
> URL: https://issues.apache.org/jira/browse/AMBARI-16919
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Swapan Shridhar
> Assignee: Swapan Shridhar
> Priority: Blocker
> Fix For: 2.4.0
>
>
> AMBARI-16888 handled the scenario when capacity-scheduler is passed in as dictionary and
> {code}
> "capacity-scheduler" : {
> "properties" : {
> "capacity-scheduler" : "null",
> "yarn.scheduler.capacity.root.accessible-node-labels" : "*",
> "yarn.scheduler.capacity.maximum-am-resource-percent" : "1",
> "yarn.scheduler.capacity.root.acl_administer_queue" : "*",
> "yarn.scheduler.capacity.queue-mappings-override.enable" : 'false',
> "yarn.scheduler.capacity.root.default.capacity" : "100",
> "yarn.scheduler.capacity.root.default.user-limit-factor" : "1",
> "yarn.scheduler.capacity.root.queues" : "default",
> "yarn.scheduler.capacity.root.capacity" : "100",
> "yarn.scheduler.capacity.root.default.acl_submit_applications" : "*",
> "yarn.scheduler.capacity.root.default.maximum-capacity" : "100",
> "yarn.scheduler.capacity.node-locality-delay" : "40",
> "yarn.scheduler.capacity.maximum-applications" : "10000",
> "yarn.scheduler.capacity.root.default.state" : "RUNNING"
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)