Add fatal JVM error handling
- Dominant language
- Java
- Stars
- 14.9k
- Forks
- 3.5k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 88
Description
We reverted #7987 due to incompatibility with Java versions below 8u92 (we support 8u60), but it would still be nice to immediately exit the JVM on OOME, or in general, any java.lang.Error.
Elasticsearch has their own mechanism for handling this (https://github.com/elastic/elasticsearch/pull/19272), and it looks good, so we maybe should copy it. Hat tip to @jasontedor for pointing it out to me.
I like ES's approach because it handles more than just OOME.
Contributor guide
Research direction
The issue names no repository files, tests, or entry points; begin by reading the linked Elasticsearch pull request and checking the Java 8u60 versus 8u92 compatibility constraint. Done means agreeing on and implementing a fatal-handling approach for java.lang.Error, including OOME, without dropping support for the stated Java versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100