[
https://issues.apache.org/jira/browse/LUCENE-6872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987659#comment-14987659
]
Mark Miller commented on LUCENE-6872:
-------------------------------------
It's really different cases I think. This is about IndexWriter handing
unrecoverable errors properly. Solr's interest in OOMExceptions is about them
bubbling up to the JVM so that you can run a script on the first one that does.
That only works with OOMException, not other VirtualMachineErrors.
> IndexWriter OOM handling should be any VirtualMachineError
> ----------------------------------------------------------
>
> Key: LUCENE-6872
> URL: https://issues.apache.org/jira/browse/LUCENE-6872
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Fix For: Trunk, 5.4
>
> Attachments: LUCENE-6872.patch
>
>
> IndexWriter is defensive in this case: this error could come from any
> unexpected place.
> But its superclass VirtualMachineError is the correct one: "Thrown to
> indicate that the Java Virtual Machine is broken or has run out of resources
> necessary for it to continue operating."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
