For people who run into this situation in the future: I had the exact same problem Sebastien had while using 4.4.0 (1 of my 6 nodes died). We rebuilt a host to take its place but gave it the same hostname instead of making a new one. It was configured the same way with the same config files but without any data of course.
When Solr on this rebuilt host got fired up, it joined ZK and the shard indexes were repopulated from the other hosts. Didn't have any issues. I think the host that died was a leader and now the rebuilt host that took its place is a replica - fine with me. I think if you pick a new hostname and the dead node kept popping up, I'd try to edit the clusterstate.json file in ZK. - Ryan On Fri, Nov 29, 2013 at 5:17 AM, Eric Bus <eric....@websight.nl> wrote: > Hi Sébastien, > > Maybe this can help? > > "Add a collection admin command to remove a replica" > https://issues.apache.org/jira/browse/SOLR-5310 > > It's part of the new 4.6.0 update. > > Best regards, > Eric > > > -----Oorspronkelijk bericht----- > Van: Seb Geek [mailto:geek...@gmail.com] > Verzonden: vrijdag 29 november 2013 12:47 > Aan: solr-user@lucene.apache.org > Onderwerp: How to remove a Solr Node and its cores from a cluster > SolrCloud and from collection > > Hello, > > I have a cluster of 4 Solr Cloud Nodes (nodes N1, N2, N3, N4). I use Solr > version 4.5.1 . One (N4) of these node have completely died (all cpu, ram > and disks are lost), I have added an other node (N5) to the Solr Cloud > cluster and copied all core configuration previously on node N4 to that > node (solr.xml and core.properties in data dir). That N5 node have > replicated all the index of my collection and is already able to respond to > request for the core (replica) that it owns. > > In the state of my Solr cloud cluster, i can see old replicas on the died > node N4 ! how can i remove theses replica from my collection ? > > Thanks > Sébastien >
