[
https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425772#comment-13425772
]
Robert Muir commented on LUCENE-4276:
-------------------------------------
{quote}
IMO, we must provide the ability to override. Changing the JVM is not trivial
in some organizations for a variety of reasons,
{quote}
Sure, I'm just saying I don't like this necessarily being some arbitrary option
we introduce. This doesn't make sense to me if we can detect the actual
workaround flags necessary to prevent the index corruption.
For the two recent corruption bugs these flags already exist, why not just use
those if we can?
* Oracle 1.7.0 b147: -XX:-UseLoopPredicate
* JRockit 1.6.0_33-R28.2.4-4.1.0: -XnoOpt
> refuse to execute on broken corrupting jvms
> -------------------------------------------
>
> Key: LUCENE-4276
> URL: https://issues.apache.org/jira/browse/LUCENE-4276
> 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 Constants.java 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
