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.

Sign up for GitHub

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

Jump to bottom

need some level of alerting should the OOM killer strike #2

Open
opaugam opened this issue Apr 1, 2015 · 0 comments
Open

need some level of alerting should the OOM killer strike #2

opaugam opened this issue Apr 1, 2015 · 0 comments

Comments

@opaugam
Copy link

opaugam commented Apr 1, 2015

I still get quite often cases where my Kafka broker gets nuked by the OOM killer. We need a way to systematically report this (ochopod will auto-restart the defunct process in any case). Not sure at this point what's the best. We could go with web-hooks..
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@opaugam