refuse to execute on broken corrupting jvms [LUCENE-4276]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
There are some jvms where we know lucene does not work at all and will just produce things like corrupt indexes.
We should detect this in a static block of Constants.java and refuse to run at all.
---
Migrated from [LUCENE-4276](https://issues.apache.org/jira/browse/LUCENE-4276) by Robert Muir (@rmuir), updated May 09 2016
Attachments: [LUCENE-4276.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4276/LUCENE-4276.patch) (versions: 3)
Contributor guide
Research direction
Start by reading Constants.java and the attached LUCENE-4276.patch to identify the JVM cases already known to corrupt indexes and how startup checks are structured. Confirm the behavior with the relevant existing tests or a minimal Lucene run; done means Lucene refuses to execute on those JVMs instead of risking index corruption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100