Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 05-21-2014 02:11 AM - edited 09-16-2022 01:59 AM
and why there is no capacity-scheduler.xml in yarn's conf folder? as described in http://hadoop.apache.org/docs/r2.3.0/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
Thanks
Created 05-21-2014 07:21 AM
See documentation here:
Dynamic Resource Pools uses the Fair Scheduler, not the Capacity Scheduler. So you don't need capacity-scheduler.xml.
Also keep in mind that cloudera doesn't generally put server-only configuration into /etc/hadoop/conf. You can view a particular role's configuration files in the CM UI on the Processes tab for that role (click Show to unhide them). These will appear in a directory in /var/run/cloudera-scm-agent/. You can see the directory name in the stderr log on the Processes tab.
Thanks,
Darren
Created 05-22-2014 02:59 AM
thanks, i found the config files that are changed
they are in
/var/run/cloudera-scm-agent/process/XXX-yarn-RESOURCEMANAGER-refresh
on yarn RM node
and
/var/run/cloudera-scm-agent/process/XXX-impala-IMPALAD/impala-conf/fair-scheduler.xml
/var/run/cloudera-scm-agent/process/XXX-impala-IMPALAD/impala-conf/llama-site.xml
on impalad node
Created 05-21-2014 07:21 AM
See documentation here:
Dynamic Resource Pools uses the Fair Scheduler, not the Capacity Scheduler. So you don't need capacity-scheduler.xml.
Also keep in mind that cloudera doesn't generally put server-only configuration into /etc/hadoop/conf. You can view a particular role's configuration files in the CM UI on the Processes tab for that role (click Show to unhide them). These will appear in a directory in /var/run/cloudera-scm-agent/. You can see the directory name in the stderr log on the Processes tab.
Thanks,
Darren
Created 05-22-2014 02:59 AM
thanks, i found the config files that are changed
they are in
/var/run/cloudera-scm-agent/process/XXX-yarn-RESOURCEMANAGER-refresh
on yarn RM node
and
/var/run/cloudera-scm-agent/process/XXX-impala-IMPALAD/impala-conf/fair-scheduler.xml
/var/run/cloudera-scm-agent/process/XXX-impala-IMPALAD/impala-conf/llama-site.xml
on impalad node
Created on 03-07-2019 09:10 AM - edited 03-07-2019 09:10 AM
Is it possible, an YARN DRP has priority against other pools?
ie. If i already have 2 DRP created
DRP1 = 500Gb
DRP2 = 200Gb
and i want to add new one DRP3 = 700Gb that have priority against other pools and use all available resources are directed to DRP3. Is this possible?
Created 04-09-2019 05:54 AM
You can try to increase the weight of the DRP3, so it will get more priority and jobs submitted to this pool will get more resources than other pools based on the weight configured.