You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Forest Soup (JIRA)" <ji...@apache.org> on 2015/03/23 10:34:11 UTC

[jira] [Created] (SOLR-7292) When there is OutOfMemory happened in Solr and Solr cannot do update, but the /clusterstates.json on ZooKeeper still shows it is "active"

Forest Soup created SOLR-7292:
---------------------------------

             Summary: When there is OutOfMemory happened in Solr and Solr cannot do update, but the /clusterstates.json on ZooKeeper still shows it is "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


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