Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
From: Deeksha Sharma <dsharma@palamida.com>
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: SolrCloud Node fails that was hosting replicas of a collection
Thread-Topic: SolrCloud Node fails that was hosting replicas of a collection
Thread-Index: AQHR081VHg2MfUstBUG3u73UxGt+XKAEc4sAgAdObiA=
Date: Wed, 6 Jul 2016 18:37:28 +0000
Message-ID: <1467830248383.60984@palamida.com>
References: <1467400702410.85539@palamida.com>,<CAN4YXvcGA27Q7ogh7uuw7G31RSqp5=ivJ1JGFq27Rsqzddccig@mail.gmail.com>
In-Reply-To: <CAN4YXvcGA27Q7ogh7uuw7G31RSqp5=ivJ1JGFq27Rsqzddccig@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
archived-at: Wed, 06 Jul 2016 18:37:41 -0000

Hi Erick,=0A=
=0A=
Thanks for your reply, but I did used the ADD REPLICA api at the first. How=
ever, since the newly added Sold node is down, it throws Exception " One of=
 the nodes is down" and hence the operation fails.=0A=
=0A=
I noticed that the node becomes GREEN only after adding the core via Admin =
UI.=0A=
Also, I am using docker containers on AWS machines to have multiple solr in=
stances running inside them. I was trying to test what will happen if one o=
f the docker containers exit and I realized this issue.=0A=
=0A=
=0A=
Thanks=0A=
Deeksha=0A=
=0A=
________________________________________=0A=
From: Erick Erickson <erickerickson@gmail.com>=0A=
Sent: Friday, July 01, 2016 12:58 PM=0A=
To: solr-user=0A=
Subject: Re: SolrCloud Node fails that was hosting replicas of a collection=
=0A=
=0A=
Please do _not_ use the admin UI core creating screen when dealing=0A=
with SolrCloud. It can work, but you have to get everything exactly=0A=
right.=0A=
=0A=
Instead, you should be using the ADDREPLICA command from the=0A=
Collections API, see:=0A=
https://cwiki.apache.org/confluence/display/solr/Collections+API=0A=
=0A=
Although I do have to ask why the Solr node is going down. If it's not some=
thing=0A=
permanent, the replicas should return to green after the node is re-started=
.=0A=
=0A=
There are plans to provide a screen in the new Admin UI to allow you=0A=
to add replicas to a collection and the like, but that code hasn't=0A=
been added yet.=0A=
=0A=
Best,=0A=
Erick=0A=
=0A=
On Fri, Jul 1, 2016 at 12:18 PM, Deeksha Sharma <dsharma@palamida.com> wrot=
e:=0A=
> Currently I am building a SolrCloud cluster with 3 Zookeepers (ensemble) =
and 4 solr instances. Cluster is hosting 4 collections and their replicas.=
=0A=
>=0A=
>=0A=
> When one Solr node say Solr1 goes down (hosting 2 replicas of collection1=
 and collection2), I add a new node to the cluster and that node in Admin U=
I is brown in color which means the new node is down.=0A=
>=0A=
>=0A=
> When I create the core on Admin UI to this new solr instance (these cores=
 are the 2 replicas that Solr1 was hosting) , the new node becomes green (u=
p and running).=0A=
>=0A=
>=0A=
> Am I doing the right thing by adding the new node and adding cores to it =
via Admin UI or there is a better way of doing this?=0A=
>=0A=
>=0A=
> Should Solr automatically host those 2 replicas to the newly added node o=
r we have to manually add cores to it?=0A=
>=0A=
>=0A=