You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ramkumar Aiyengar (JIRA)" <ji...@apache.org> on 2015/03/24 09:04:52 UTC

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

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

Ramkumar Aiyengar closed SOLR-7292.
-----------------------------------
    Resolution: Won't Fix

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