Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
he-sk opened this issue Jun 25, 2019 · 4 comments
Open

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

he-sk opened this issue Jun 25, 2019 · 4 comments

Comments

@he-sk
Copy link

he-sk commented Jun 25, 2019

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.

@Vasuki-munirathinam
Copy link

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
Copy link
Author

he-sk commented May 24, 2023

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

@Vasuki-munirathinam
Copy link

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
Copy link
Author

he-sk commented May 31, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants