[
https://issues.apache.org/jira/browse/SOLR-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834628#comment-13834628
]
Ricardo Merizalde commented on SOLR-5216:
-----------------------------------------
Mark, can this issue affect SolrCloud deployments with a single shard? We've
been running SolrCloud since April and we experienced an odd outage today we've
never seen before.
We are currently running Solr 4.5.1 with 4 slaves and we use CloudSolrServer to
send updates. The number of threads went from under 100 to almost 400 in each
of the instances in less than one minute. The heap filled up quickly as well
until they ran out of memory. It filled about 2GB worth of heap in a couple
minutes. Of course, all four JVM started doing major collections one after
another but couldn't free any heap memory.
Unfortunately, we forgot to take thread dumps in the rush for recovering our
site. All we have are the heap dumps.
Also, we do auto hard commits every 5 minutes or every 10k documents.
We'll be trying 4.6 soon, however I want to check if we are headed in the right
direction.
> Document updates to SolrCloud can cause a distributed deadlock.
> ---------------------------------------------------------------
>
> Key: SOLR-5216
> URL: https://issues.apache.org/jira/browse/SOLR-5216
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 4.6, 5.0
>
> Attachments: SOLR-5216.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
