lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4276) refuse to execute on broken corrupting jvms
Date Tue, 31 Jul 2012 13:55:35 GMT


Jack Krupansky commented on LUCENE-4276:

What I would prefer to have is a tool/script that I can explicitly run that will alert me
to potential issues before I even run Lucene/Solr on a box. Or maybe both a command line tool
and a test app that can be deployed in the desired container to report potential issues.

Then, as part of the support process, the first thing we would ask people is whether they
ran the "environment check" tool and what it said.

The JVM/compatibility check is just one example of checks that the tool could perform.

> refuse to execute on broken corrupting jvms
> -------------------------------------------
>                 Key: LUCENE-4276
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>            Priority: Blocker
>             Fix For: 4.0
>         Attachments: LUCENE-4276.patch
> 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 and refuse to run at all.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message