Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
2.1.2
-
None
-
SLES 11
Description
service check failing for some services if custom capacity scheduler is enabled with out default queue.
Configure mydefault queue instead of default queue like below in YARN config.
yarn.scheduler.capacity.root.queues=mydefault
yarn.scheduler.capacity.root.mydefault.user-limit-factor=1
yarn.scheduler.capacity.root.mydefault.state=RUNNING
yarn.scheduler.capacity.root.mydefault.maximum-capacity=100
yarn.scheduler.capacity.root.mydefault.capacity=100
yarn.scheduler.capacity.root.mydefault.acl_administer_jobs=*
yarn.scheduler.capacity.root.default.acl_submit_applications=*
yarn.scheduler.capacity.root.capacity=100
yarn.scheduler.capacity.root.acl_administer_queue=*
yarn.scheduler.capacity.root.accessible-node-labels=*
yarn.scheduler.capacity.node-locality-delay=40
yarn.scheduler.capacity.mydefault.minimum-user-limit-percent=100
yarn.scheduler.capacity.maximum-applications=10000
yarn.scheduler.capacity.maximum-am-resource-percent=0.2
and restart affected components.
Run service check for oozie. You will see that fail.
We need to maintain default queue just to test service check for some services.
I can not have different name for my default queue. I have to allocate some resources for default queue for the sake of service checks.