Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Resource manager does not Start After Changes in Capacity Scheduler.

Resource manager does not Start After Changes in Capacity Scheduler.

New Contributor

I added a couple of queues (q1, q2) to the already existing 2 queues (llap and default) in my capacity scheduler and set the parameters accordingly. I divided the cluster resources as: q1: 20, q2: 20, default: 0, llap: 60.

Now the resource manager does not start. When I try to restart it, it successfully starts and stops withing seconds.

I read other answers to disable the property: yarn.scheduler.capacity.root.accessible-node-labels.default.capacity but I can not even find this property in the xml file nor in Ambari.

Can someone please suggest where I should start debugging this?

2 REPLIES 2
Highlighted

Re: Resource manager does not Start After Changes in Capacity Scheduler.

Hi @Sree Kupp,

Can you please check ResourceManager logs and see what type error it is throwing?

Please attach ResourceManager logs and capacityScheduler.xml ??

Re: Resource manager does not Start After Changes in Capacity Scheduler.

New Contributor

Thank you @ssathish for your answer, my colleague had set wrong capacity values for the queues and it added up to > 100%. We were able to resolve it.