Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of static.void.dev@gmail.com
 designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
Date: Sat, 22 Mar 2014 12:23:40 -0700
Message-ID: 
 <CAH-BiJj9WGRwALO5T3tUr-fhHXJz2PuVrJ3bu1W8GmtOKqLr1w@mail.gmail.com>
Subject: Solr Cloud collection keep going down?
From: Software Dev <static.void.dev@gmail.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=089e013a0dbc95c10604f536f0bf

--089e013a0dbc95c10604f536f0bf
Content-Type: text/plain; charset=ISO-8859-1

We have 2 collections with 1 shard each replicated over 5 servers in the
cluster. We see a lot of flapping (down or recovering) on one of the
collections. When this happens the other collection hosted on the same
machine is still marked as active. When this happens it takes a fairly long
time (~30 minutes) for the collection to come back online, if at all. I
find that its usually more reliable to completely shutdown solr on the
affected machine and bring it back up with its core disabled. We then
re-enable the core when its marked as active.

A few questions:

1) What is the healthcheck in Solr-Cloud? Put another way, what is failing
that marks one collection as down but the other on the same machine as up?

2) Why does recovery take forever when a node goes down.. even if its only
down for 30 seconds. Our index is only 7-8G and we are running on SSD's.

3) What can be done to diagnose and fix this problem?

--089e013a0dbc95c10604f536f0bf--