Need your inputs and expertise on this topic.
1. I have configured a FAIR_TEST queue and set the Ordering to FAIR
2. Have added "fair-scheduler.xml" in HADOOP_CONF_DIR default path (/usr/hdp/220.127.116.11-78/hadoop/conf) and have set minResources and maxResources to 4 GB and 8 GB respectively.
3. Changed the Scheduler Class in Ambari to fair scheduler class and added a parameter "yarn.scheduler.fair.allocation.file" to point to the above XML file.
While re-starting the YARN affected components in Ambari, I am getting the below error:
Can you please let me know what's going wrong and how to fix this issue.
2019-12-19 09:48:17,762 INFO service.AbstractService (AbstractService.java:noteFailure(267)) - Service NodeManager failed in state INITED
java.lang.RuntimeException: java.lang.RuntimeException: class org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler not org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor
Caused by: java.lang.RuntimeException: class org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler not org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor
<rule name="specified" />
<rule name="default" queue="FAIR-TEST" />
Any updates on the below issue? I am facing lot of hurdles in getting this fixed.
I would appreciate any quick inputs from any one in fixing the problem.
@jsensharma @nsabharwal - I am a newbie to Cloudera Community and have seen that both of you are Gurus. Can you please help me in fixing this issue?
Thanks and Regards,
Can you please help?
It has been almost a week since I am stuck at the same issue. I would appreciate any quick help on this critical issue, which is blocking my tasks.
Thanks and Regards,
I successfully configured the fair scheduler on the below HDP version
Default capacity scheduler after deployment of HDP
Pre-emption enabled before the change to fair-scheduler
Grabbed the template fair-scheduler.xml fair-scheduler here I then changed a few values for testing purposes but ensured the is valid using the XML using XML Validator I then copied the fair-scheduler.xml to the $HADOOP_CONF directory and changed the user & permission
# cd /usr/hdp/18.104.22.168-78/hadoop/conf
# chown hdfs:hadoop fair-scheduler.xml
# chmod 644 fair-scheduler.xml
Changed the Scheduler class in the yarn-site.xml see the attached screenshot.
From : yarn.resourcemanager.scheduler.class=org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler
Added these new values in Custom yarn-site using the relative path default to /usr/hdp/22.214.171.124-78/hadoop/conf
Changed the below mandatory parameter to enable the ReservationSystem in the ResourceManager is not enabled by default
Set the below properties as shown
The yarn-site.xml file contains parameters that determine scheduler-wide options. These properties include the below properties if they don't exist add them in the custom yarn-site
The below property was available so I didn't add
Properties to verify
For my testing I didn't add the below properties, you will notice that above that despite disabling the pre-emption in the Ambari UI the fair schedule shows it's enabled [True] and my queues ain't showing I need to check my fair-scheduler.xml attached is the template I used
yarn.scheduler.fair.preemption=false Note: Do not use preemption when FairScheduler DominantResourceFairness is in
use and node labels are present.
All in all, this shows the fair-scheduler configuration is doable and my RM is up and running !!
I also noticed that the above fair-scheduler was template overwritten when I checked the YARN Queue Manager so that can now allow me to configure a new valid fair-scheduler
Thanks for the reply. I have been able to change the scheduling mode to Fair-Scheduler, which is great.
However, my application is not running, due to resource allocation issue. I am getting the below standard error.
|[Mon Dec 30 15:02:19 +0530 2019] Application is added to the scheduler and is not yet activated. (Resource request: <memory:1024, vCores:1> exceeds maximum AM resource allowed).|
I am attaching all the relevant screenshots as well as information of my Yarn cluster for your reference.
Please guide me in fixing this issue. Why this issue usually occurs.
My YARN cluster has 2 nodes, scheduling mode as "Fair-Scheduler", minimum allocation of 1 GB/1 vcores and maximum allocation of 15GB/3 vcores and overall memory is 30GB.
Given below is "fair-scheduler.xml" contents:
Below is the custom yarn-site parameters that have been set and the preemption is disabled as well.
Please help me on this. I am again stuck on the issue. Did I wrongly configure anything?
Also, even after setting preemption to false, in the YARN Resource Manager UI, I am able to see that the preemption is still enabled. Is this causing the problem?
Thanks and Regards,
Hi @Shelton ,
I have made some progress on this issue. I have modified the fair-scheduler.xml and have set both "maxAMShare" and "queueMaxAMShareDefault" to 0.8 and weight to default value (1.0).
The result: One spark job is running fine. However, I am getting the same error as before on the exceeding of maximum AM resources limit, when I try to run the next job.
The modified fair-scheduler.xml is given below. Please provide your inputs on how to fix this particular issue.
Also, one interesting observation is that, even though the YARN Scheduling mode is showing as "Fair", the Spark Scheduling mode is still showing as "FIFO". Can I set it to "Fair" as well through the program? Since I am setting spark.master as "YARN", I believe the Fair scheduling mode will take precedence over the Spark scheduling mode. Please correct me if I am wrong.
A queueMaxAMShareDefault and maxAMShare are mutually exclusive as its overridden by maxAMShare element in each queue.
Can you decrease it to queueMaxAMShareDefault or maxAMShare to 0.1 and weight to 2.0
For the spark create the fairscheduler.xml from the fairscheduler.xml.template
your path might be different due to version 3.1.x.x.x.
# cp /usr/hdp/3.1.x.x-xx/etc/spark2/conf/fairscheduler.xml.template fairscheduler.xml
Please check the file permission
Then set spark.scheduler.allocation.file property in your SparkConf or either by putting a file named fairscheduler.xml on the classpath.
Note if no pools configured in the XML file will simply get default values for all settings (scheduling mode FIFO, weight 1, and minShare 0).
Here there are 2 default pools in fairscheduler.xml.template notably production and test using FAIR and FIFO
Without any intervention, newly submitted jobs go into a default pool, but jobs’ pools can be set by adding the spark.scheduler.pool “local property” to the SparkContext in the thread that’s submitting them. This is done as follows:
// Assuming sc is your SparkContext variable to pick the FAIR
Please let me know