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

Notes on diagnosing the cause of Zeppelin/Spark/Yarn failures #566

Merged
merged 1 commit into from
Aug 26, 2021

Conversation

Zarquan
Copy link
Collaborator

@Zarquan Zarquan commented Aug 26, 2021

No description provided.

@NigelHambly
Copy link
Collaborator

The contents of that file are all Greek to me ... over to Stelios :)


hs_err_pid27205.log
"There is insufficient memory for the Java Runtime Environment to continue."

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So these are two separate issues? Or are they related?

Issue 1: Zeppelin ran out of disk space due to log files
Issue 2: Worker nodes dies with out of memory exceptions

Any hints in Grafana/Prometheus? We should be able to go back and check resources usage at the time if the monitor node wasn't killed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Separate issues that happened at separate times.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to do some more work on the Grafana/Prometheus dashboards before we can get really useful information out of them.
Getting there, but not the primary information source yet.

@stvoutsin stvoutsin merged commit 9e31860 into wfau:master Aug 26, 2021
@Zarquan Zarquan deleted the 20210826-zrq-crash-debug branch August 26, 2021 18:57
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

Successfully merging this pull request may close these issues.

3 participants