Support Questions

Find answers, ask questions, and share your expertise

Yarn can"t add sub queue (hdp - 2.6.3 )

Contributor

64533-add-sub-queue.png

Try add sub queue airflow (in root.aggregate), but can not save change

3 REPLIES 3

Rising Star

Contributor

Hi!

Thank you, it is works. One more question, how add user mapping on “sub-queue” ? :

Example like this not working : yarn.scheduler.capacity.queue-mappings=u:airflow:aggregate.airflow

yarn.scheduler.capacity.maximum-am-resource-percent=0.6
yarn.scheduler.capacity.maximum-applications=10000
yarn.scheduler.capacity.node-locality-delay=40
yarn.scheduler.capacity.root.accessible-node-labels=*
yarn.scheduler.capacity.root.acl_administer_queue=*
yarn.scheduler.capacity.root.capacity=100
yarn.scheduler.capacity.root.default.acl_submit_applications=*
yarn.scheduler.capacity.root.default.capacity=10
yarn.scheduler.capacity.root.default.maximum-capacity=40
yarn.scheduler.capacity.root.default.state=RUNNING
yarn.scheduler.capacity.root.default.user-limit-factor=0.7
yarn.scheduler.capacity.root.queues=aggregate,default,llap,load,reports
yarn.scheduler.capacity.root.aggregate.queues=airflow          <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
yarn.scheduler.capacity.queue-mappings=u:airflow:aggregate.airflow  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<,
yarn.scheduler.capacity.queue-mappings-override.enable=true
yarn.scheduler.capacity.root.aggregate.acl_submit_applications=*
yarn.scheduler.capacity.root.aggregate.capacity=35
yarn.scheduler.capacity.root.aggregate.maximum-am-resource-percent=1
yarn.scheduler.capacity.root.aggregate.maximum-applications=20000
yarn.scheduler.capacity.root.aggregate.maximum-capacity=60
yarn.scheduler.capacity.root.aggregate.minimum-user-limit-percent=10
yarn.scheduler.capacity.root.aggregate.state=RUNNING
yarn.scheduler.capacity.root.aggregate.user-limit-factor=0.7
yarn.scheduler.capacity.root.aggregate.airflow.acl_submit_applications=*
yarn.scheduler.capacity.root.aggregate.airflow.capacity=100
yarn.scheduler.capacity.root.aggregate.airflow.maximum-am-resource-percent=1
yarn.scheduler.capacity.root.aggregate.airflow.maximum-applications=20000
yarn.scheduler.capacity.root.aggregate.airflow.maximum-capacity=100
yarn.scheduler.capacity.root.aggregate.airflow.minimum-user-limit-percent=10
yarn.scheduler.capacity.root.aggregate.airflow.state=RUNNING
yarn.scheduler.capacity.root.aggregate.airflow.user-limit-factor=0.5
yarn.scheduler.capacity.root.default.maximum-am-resource-percent=1
yarn.scheduler.capacity.root.default.maximum-applications=20000
yarn.scheduler.capacity.root.default.minimum-user-limit-percent=10
yarn.scheduler.capacity.root.default.priority=0
yarn.scheduler.capacity.root.llap.acl_administer_queue=*
yarn.scheduler.capacity.root.llap.acl_submit_applications=*
yarn.scheduler.capacity.root.llap.capacity=0
yarn.scheduler.capacity.root.llap.maximum-am-resource-percent=1
yarn.scheduler.capacity.root.llap.maximum-capacity=0
yarn.scheduler.capacity.root.llap.minimum-user-limit-percent=100
yarn.scheduler.capacity.root.llap.ordering-policy=fifo
yarn.scheduler.capacity.root.llap.priority=0
yarn.scheduler.capacity.root.llap.state=STOPPED
yarn.scheduler.capacity.root.llap.user-limit-factor=1
yarn.scheduler.capacity.root.load.acl_submit_applications=*
yarn.scheduler.capacity.root.load.capacity=45
yarn.scheduler.capacity.root.load.maximum-am-resource-percent=1
yarn.scheduler.capacity.root.load.maximum-applications=20000
yarn.scheduler.capacity.root.load.maximum-capacity=80
yarn.scheduler.capacity.root.load.minimum-user-limit-percent=10
yarn.scheduler.capacity.root.load.ordering-policy=fair
yarn.scheduler.capacity.root.load.ordering-policy.fair.enable-size-based-weight=false
yarn.scheduler.capacity.root.load.priority=1
yarn.scheduler.capacity.root.load.state=RUNNING
yarn.scheduler.capacity.root.load.user-limit-factor=0.7
yarn.scheduler.capacity.root.ordering-policy=priority-utilization
yarn.scheduler.capacity.root.priority=0
yarn.scheduler.capacity.root.reports.acl_submit_applications=*
yarn.scheduler.capacity.root.reports.capacity=10
yarn.scheduler.capacity.root.reports.maximum-am-resource-percent=0.4
yarn.scheduler.capacity.root.reports.maximum-capacity=10
yarn.scheduler.capacity.root.reports.minimum-user-limit-percent=5
yarn.scheduler.capacity.root.reports.priority=0
yarn.scheduler.capacity.root.reports.state=RUNNING
yarn.scheduler.capacity.root.reports.user-limit-factor=0.5


<br>

Contributor

Hi All! One more question, how add user mapping on “sub-queue” ?