Hello all,
Is there a way to isolate an active solr-cloud instance from all incoming
replication update requests from peer nodes ?
--
Regards,
-Aditya Sakhuja
ted per node.
>
> On Thu, Sep 12, 2013 at 3:19 AM, Aditya Sakhuja
> wrote:
> > Hi -
> >
> > I am trying to set the 3 shards and 3 replicas for my solrcloud
> deployment
> > with 3 servers, specifying the replicationFactor=3 and numShards=3 when
> > starting
How does one recover from an index corruption ? That's what I am trying to
eventually tackle here.
Thanks
Aditya
On Thursday, September 19, 2013, Aditya Sakhuja wrote:
> Hi,
>
> Sorry for the late followup on this. Let me put in more details here.
>
> *The problem:*
>
a from the index directory on a restart ?
Thanks in advance,
Aditya
On Fri, Sep 6, 2013 at 3:41 PM, Aditya Sakhuja wrote:
> Thanks Shalin and Mark for your responses. I am on the same page about the
> conventions for taking the backup. However, I am less sure about the
> restoration
specifically need to have 3 replicas across 3 servers with 3 shards. Do
we think of any reason to not have this configuration ?
--
Regards,
-Aditya Sakhuja
>> updates, commit your changes and then take a backup, you will likely
> >> miss some updates.
> >>
> >> That being said, I'm curious to see how peer sync behaves when you try
> >> to restore from a snapshot. When you say that you haven't been
&g
index.properties along with
the second version.
--
Regards,
-Aditya Sakhuja
, but
still relevant if you tested with a previous version.
I haven't been successful in have the restored index replicate across the
new replicas, after I restart all the nodes, with one node having the
restored index.
Is restoring the indexes on all the nodes the best way to do it ?
--
Regard
for future solrcloud 4.5.
I would appreciate if someone can confirm this for solr 4.1 ?
My second question is : Is it ok to have different commit types on
different nodes which are part of my solrCloud deployment ?
Regards,
Aditya
--
Regards,
-Aditya Sakhuja