[
https://issues.apache.org/jira/browse/AMBARI-11228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-11228:
------------------------------------
Description:
STEPS TO REPRODUCE: This is a contrived example, but, demonstrates what happens
when the capacity scheduler is configured in such scenarios.
1) Take the following capacity scheduler settings and paste them in to the
Capacity Scheduler settings in Ambari, then restart YARN:
{code:java}
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.queue-mappings=u:%user:%user
yarn.scheduler.capacity.queue-mappings-override.enable=true
yarn.scheduler.capacity.root.acl_administer_queue=*
yarn.scheduler.capacity.root.capacity=100
yarn.scheduler.capacity.root.hdfs.acl_administer_jobs=*
yarn.scheduler.capacity.root.hdfs.acl_administer_queue=*
yarn.scheduler.capacity.root.hdfs.acl_submit_applications=hdfs
yarn.scheduler.capacity.root.hdfs.acl_submit_jobs=hdfs
yarn.scheduler.capacity.root.hdfs.capacity=20
yarn.scheduler.capacity.root.hdfs.maximum-capacity=100
yarn.scheduler.capacity.root.hdfs.state=RUNNING
yarn.scheduler.capacity.root.hdfs.user-limit-factor=1
yarn.scheduler.capacity.root.hive.acl_administer_jobs=*
yarn.scheduler.capacity.root.hive.acl_administer_queue=*
yarn.scheduler.capacity.root.hive.acl_submit_applications=hive
yarn.scheduler.capacity.root.hive.acl_submit_jobs=hive
yarn.scheduler.capacity.root.hive.capacity=20
yarn.scheduler.capacity.root.hive.maximum-capacity=100
yarn.scheduler.capacity.root.hive.state=RUNNING
yarn.scheduler.capacity.root.hive.user-limit-factor=1
yarn.scheduler.capacity.root.queues=newuser,hive,hdfs
yarn.scheduler.capacity.root.newuser.acl_administer_jobs=*
yarn.scheduler.capacity.root.newuser.acl_administer_queue=*
yarn.scheduler.capacity.root.newuser.acl_submit_applications=newuser
yarn.scheduler.capacity.root.newuser.acl_submit_jobs=newuser
yarn.scheduler.capacity.root.newuser.capacity=60
yarn.scheduler.capacity.root.newuser.minimumaximum-capacity=100
yarn.scheduler.capacity.root.newuser.state=RUNNING
yarn.scheduler.capacity.root.newuser.user-limit-factor=1
yarn.scheduler.capacity.root.unfunded.capacity=50
{code}
2) Kick off any service check that would leverage the use of YARN (such as Pig,
Oozie, or MRv2).
ACTUAL RESULTS - The service check fails with the attached errors.
> Validate capacity scheduler configurations
> ------------------------------------------
>
> Key: AMBARI-11228
> URL: https://issues.apache.org/jira/browse/AMBARI-11228
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Fix For: 2.2.0
>
>
> STEPS TO REPRODUCE: This is a contrived example, but, demonstrates what
> happens when the capacity scheduler is configured in such scenarios.
> 1) Take the following capacity scheduler settings and paste them in to the
> Capacity Scheduler settings in Ambari, then restart YARN:
> {code:java}
> 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.queue-mappings=u:%user:%user
> yarn.scheduler.capacity.queue-mappings-override.enable=true
> yarn.scheduler.capacity.root.acl_administer_queue=*
> yarn.scheduler.capacity.root.capacity=100
> yarn.scheduler.capacity.root.hdfs.acl_administer_jobs=*
> yarn.scheduler.capacity.root.hdfs.acl_administer_queue=*
> yarn.scheduler.capacity.root.hdfs.acl_submit_applications=hdfs
> yarn.scheduler.capacity.root.hdfs.acl_submit_jobs=hdfs
> yarn.scheduler.capacity.root.hdfs.capacity=20
> yarn.scheduler.capacity.root.hdfs.maximum-capacity=100
> yarn.scheduler.capacity.root.hdfs.state=RUNNING
> yarn.scheduler.capacity.root.hdfs.user-limit-factor=1
> yarn.scheduler.capacity.root.hive.acl_administer_jobs=*
> yarn.scheduler.capacity.root.hive.acl_administer_queue=*
> yarn.scheduler.capacity.root.hive.acl_submit_applications=hive
> yarn.scheduler.capacity.root.hive.acl_submit_jobs=hive
> yarn.scheduler.capacity.root.hive.capacity=20
> yarn.scheduler.capacity.root.hive.maximum-capacity=100
> yarn.scheduler.capacity.root.hive.state=RUNNING
> yarn.scheduler.capacity.root.hive.user-limit-factor=1
> yarn.scheduler.capacity.root.queues=newuser,hive,hdfs
> yarn.scheduler.capacity.root.newuser.acl_administer_jobs=*
> yarn.scheduler.capacity.root.newuser.acl_administer_queue=*
> yarn.scheduler.capacity.root.newuser.acl_submit_applications=newuser
> yarn.scheduler.capacity.root.newuser.acl_submit_jobs=newuser
> yarn.scheduler.capacity.root.newuser.capacity=60
> yarn.scheduler.capacity.root.newuser.minimumaximum-capacity=100
> yarn.scheduler.capacity.root.newuser.state=RUNNING
> yarn.scheduler.capacity.root.newuser.user-limit-factor=1
> yarn.scheduler.capacity.root.unfunded.capacity=50
> {code}
> 2) Kick off any service check that would leverage the use of YARN (such as
> Pig, Oozie, or MRv2).
> ACTUAL RESULTS - The service check fails with the attached errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
