Phone typing. The end should not say "don't hard commit" - it should say "do a hard commit and take a snapshot".
Mark Sent from my iPhone On Sep 6, 2013, at 7:26 AM, Mark Miller <markrmil...@gmail.com> wrote: > I don't know that it's too bad though - its always been the case that if you > do a backup while indexing, it's just going to get up to the last hard > commit. With SolrCloud that will still be the case. So just make sure you do > a hard commit right before taking the backup - yes, it might miss a few docs > in the tran log, but if you are taking a back up while indexing, you don't > have great precision in any case - you will roughly get a snapshot for around > that time - even without SolrCloud, if you are worried about precision and > getting every update into that backup, you want to stop indexing and commit > first. But if you just want a rough snapshot for around that time, in both > cases you can still just don't hard commit and take a snapshot. > > Mark > > Sent from my iPhone > > On Sep 6, 2013, at 1:13 AM, Shalin Shekhar Mangar <shalinman...@gmail.com> > wrote: > >> The replication handler's backup command was built for pre-SolrCloud. >> It takes a snapshot of the index but it is unaware of the transaction >> log which is a key component in SolrCloud. Hence unless you stop >> 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 >> successful in restoring, what exactly is the behaviour you observed? >> >> On Fri, Sep 6, 2013 at 5:14 AM, Aditya Sakhuja <aditya.sakh...@gmail.com> >> wrote: >>> Hello, >>> >>> I was looking for a good backup / recovery solution for the solrcloud >>> indexes. I am more looking for restoring the indexes from the index >>> snapshot, which can be taken using the replicationHandler's backup command. >>> >>> I am looking for something that works with solrcloud 4.3 eventually, 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 ? >>> -- >>> Regards, >>> -Aditya Sakhuja >> >> >> >> -- >> Regards, >> Shalin Shekhar Mangar.
