sorry there is a typo on earlier message.. I didn't make any changes in autoscalling policies/triggers
On Thu, Aug 27, 2020 at 12:12 PM yaswanth kumar <yaswanth...@gmail.com> wrote: > Thanks for looking into this. > > I did used replication factor as 3 with autoAddReplica=true, and did make > any changes in autoscalling policies/triggers everything is defaults that > comes with solr. > > On Thu, Aug 27, 2020 at 11:50 AM Howard Gonzalez < > howard.gonza...@careerbuilder.com> wrote: > >> Hi, could you share the replication factor that you're using for those >> collections (in case they are NRT replicas)? DId you make any changes in >> autoscaling policies/triggers? >> ________________________________ >> From: yaswanth kumar <yaswanth...@gmail.com> >> Sent: Thursday, August 27, 2020 11:37 AM >> To: solr-user@lucene.apache.org <solr-user@lucene.apache.org> >> Subject: New replica is being added to existing collections upon server >> reboot >> >> Can someone help me understand on why the below is happening? >> >> Solr: 8.2; Zookeer:3.5 >> >> One zookeeper + 3 solr nodes >> >> Initially created multiple collections with 3 replicas , indexed data >> everything looked great. >> >> We now restarted all 3 solr nodes, and we started the zookeeper and solr >> services , cloud came back good but on each collection we are now seeing a >> 4th replica and that is in down status. Other than this additional node >> every other operation is working fine. >> >> Please let me know on what case this could happen, also want to know if >> there is any easy way to get rid of the 4th newly added down solr replica >> for all collections. >> >> -- >> Thanks & Regards, >> Yaswanth Kumar Konathala. >> yaswanth...@gmail.com >> > > > -- > Thanks & Regards, > Yaswanth Kumar Konathala. > yaswanth...@gmail.com > -- Thanks & Regards, Yaswanth Kumar Konathala. yaswanth...@gmail.com
