search

E2Data / E2DataYARN

Modified version of YARN that supports fine-grained control on accelerators of the same type
1 stars 0 forks source link

NodeManager does not start when the naming scheme is not followed #2

Open he-sk opened 5 years ago

he-sk commented 5 years ago

When the naming scheme is not followed (i.e., yarn.io/gpu instead of yarn.io/gpu-geforcegtx1080), start-yarn.sh prints a cryptic error message:

$ sbin/start-yarn.sh
Starting resourcemanager
Starting nodemanagers
localhost: ERROR: Cannot set priority of nodemanager process 15665

This error is caused by an java.lang.ArrayIndexOutOfBoundsException because the split in the following line does not work as expected. This error should be handled more gracefully.

https://github.com/E2Data/E2DataYARN/blob/2842739cbdce50df47aae0f77a1d33af7a4a65ff/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/resourceplugin/ResourcePluginManager.java#L92

Vasuki-munirathinam commented 1 year ago

so what is the solution for this ~/hadoop-3.2.3/sbin$ start-yarn.sh Starting resourcemanager ERROR: Cannot set priority of resourcemanager process 9834 Starting nodemanagers localhost: ERROR: Cannot set priority of nodemanager process 9944

he-sk commented 1 year ago

@Vasuki-munirathinam Is this Hadoop instance installed through Peel or manually?

Vasuki-munirathinam commented 1 year ago

Yeah it is installed manually and i rectified that error The oracle jdk version i have used is latest so i switched to 8.1 version.

he-sk commented 1 year ago

Does the error also occur when installed through Peel? That is the workflow that we support.