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: 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+XA==
Date: Fri, 1 Jul 2016 19:18:23 +0000
Message-ID: <1467400702410.85539@palamida.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_146740070241085539palamidacom_"
MIME-Version: 1.0
archived-at: Fri, 01 Jul 2016 19:18:36 -0000

--_000_146740070241085539palamidacom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Currently I am building a SolrCloud cluster with 3 Zookeepers (ensemble) an=
d 4 solr instances. Cluster is hosting 4 collections and their replicas.


When one Solr node say Solr1 goes down (hosting 2 replicas of collection1 a=
nd collection2), I add a new node to the cluster and that node in Admin UI =
is brown in color which means the new node is down.


When I create the core on Admin UI to this new solr instance (these cores a=
re the 2 replicas that Solr1 was hosting) , the new node becomes green (up =
and running).


Am I doing the right thing by adding the new node and adding cores to it vi=
a Admin UI or there is a better way of doing this?


Should Solr automatically host those 2 replicas to the newly added node or =
we have to manually add cores to it?


--_000_146740070241085539palamidacom_--