-
Notifications
You must be signed in to change notification settings - Fork 149
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
[Improvement] Exit on OutOfMemoryError #460
Comments
PTAL @jerqi @zuston @advancedxy |
Do we need dump the memory when OOM occurs? |
The dump file maybe too big and disk space may be not enough to store it. So users should specify the path to store it. |
+1 from my side. oom dump should be an opt-in feature. The bin/start-shuffle-server.sh may handle that as a cli argument or env variable. |
Good idea. This should be supported. |
Requesting permission to contribute to this feature. . Can you please advise on how I can get involved? Thanks |
I assigned this issue to you. |
@jerqi Could you kindly provide me with additional resources and guidance [files to change, tests to perform], please? |
1 files to change https://github.com/apache/incubator-uniffle/blob/master/bin/start-coordinator.sh 2 test to perform |
@AdarshRawat1 Do you need any other help from me? |
@jerqi I’m currently occupied with my mid-term exams. Once I’m done with them, I’ll address this issue. I would appreciate your valuable guidance at that time. Thank you. |
@AdarshRawat1 Do you want to continue this issue? |
@jerqi I deeply regret the delay and will commence work on it today. I look forward to receiving your guidance throughout the process. |
OK. I will give some guidance. |
@jerqi I apologize, but I'm unable to work on this issue. |
### What changes were proposed in this pull request? Exit on OutOfMemoryError to specify JVM options ### Why are the changes needed? Fix: #460 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Tested on production env
Code of Conduct
Search before asking
What would you like to be improved?
At present, if OutOfMemoryError is encountered, server will not exit.
How should we improve?
Add
-XX:+ExitOnOutOfMemoryError
and-XX:+CrashOnOutOfMemoryError
to JVM argments.Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: