Sorry - just got back to this
1. We can standup the AWS resources quickly (~ 30 mins) but the process of
repopulating the index is very slow (< 1k docs per second). We need to fix
this but I¹m hoping to a backup solution would be a mitigation in the
meantime.
2. Yes we have autoscaling (with a
...@johnbickerstaff.com]
Sent: Thursday, February 8, 2018 4:06 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud: How best to do backups?
This article may be of some use...
What isn't clear is what effect either of the two strategies mentioned would
have on serving responses to queries... It would
This article may be of some use...
What isn't clear is what effect either of the two strategies mentioned
would have on serving responses to queries... It would be nice if the
backup was a "low priority thread" compared to the needs of the server in
question, but I've never had to dig that deep
Hmmm...
Can you (fairly quickly) reproduce this AWS environment (including the
indexes)? Or does it require that several week process to provision new
Solr boxes...?
What happens now if one of those ec2 instances gets into trouble? Do you
have autoscaling groups set up?
On Thu, Feb 8, 2018 at
We have a large SolrCloud deployment on AWS (350m documents spread across 3
collections, each with 3 shards and 3 replicas)
Running on 3 x r3.xlarge’s with the data stored on EBS drives with Provisioned
IOPS
Currently it’s handling 38m requests per day
My question is how best should we back-up
