[
https://issues.apache.org/jira/browse/SOLR-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376646#comment-14376646
]
Ramkumar Aiyengar commented on SOLR-7292:
-----------------------------------------
I agree with Shawn here, the foolproof way is to just kill Solr through an OOM
handler. That will still not update cluster state as the shutdown is not clean.
However, ZK will remove the live node for the cores in the JVM, and all of
Solr's distributed logic consider both of these pieces of information. Even if
Solr handled OOME, that operation will need memory and that might fail as well..
> OutOfMemory happened in Solr, but /clusterstates.json shows cores "active"
> --------------------------------------------------------------------------
>
> Key: SOLR-7292
> URL: https://issues.apache.org/jira/browse/SOLR-7292
> Project: Solr
> Issue Type: Bug
> Components: contrib - Clustering
> Affects Versions: 4.7
> Environment: Redhat Linux 6.3 64bit
> Reporter: Forest Soup
> Labels: performance
> Attachments: OOM.txt, failure.txt
>
>
> One of our 5 Solr server got OOM, but in /clusterstates.json in ZK, it is
> still "active". The OOM Ex are the attached OOM.txt.
> But update and commit to the collection which has cores on that Solr server
> will got failure. The logs are in the failure.txt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
