[jira] [Updated] (SOLR-7292) OutOfMemory happened in Solr, but /clusterstates.json shows cores "active"

["Forest Soup (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Forest Soup updated SOLR-7292:
------------------------------
    Summary: OutOfMemory happened in Solr, but /clusterstates.json shows cores "active"  (was: When there is OutOfMemory happened in Solr and Solr cannot do update, but the /clusterstates.json on ZooKeeper still shows it is "active")

> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org