-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add exit_on_oom=true #744
Add exit_on_oom=true #744
Conversation
Makefile
Outdated
@@ -1,5 +1,5 @@ | |||
# Current Operator version | |||
VERSION ?= 0.20.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should only be updated when do release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why would we not want to release this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also, the version on master is incorrect anyways, there is a v0.20.1 release on dockerhub already
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just comment: no need to change anything.
when jvm requests to allocate more "direct memory" and failed, it is not oom. It is just failed to allocate memory.
Motivation
Exit the client when it is OOM Killed.
Modifications
Add
-Dpulsar.allocator.exit_on_oom=true
to common.goVerifying this change
This change is a trivial rework / code cleanup without any test coverage.
Documentation
Need to update docs?
no-need-doc
Internals change resolving a bug.