I also want to know how to realization it.
--
View this message in context:
http://lucene.472066.n3.nabble.com/solrcloud-shards-backup-restoration-tp4088447p4138358.html
Sent from the Solr - User mailing list archive at Nabble.com.
We've managed some success restoring existing/backed up indexes into solr cloud
and even building the indexes offline and dumping the lucene files into the
directories that solr expects. The general steps we follow are:
1) Round up your files. It doesn't matter if you pull from a master or slave
Any update on this ?
I am also stuck with same problem, I want to install snapshot of master solr
server to my local environment. but i could't :(
All most spend 2 days to figure it out the way. Please help!!
--
View this message in context:
http://lucene.472066.n3.nabble.com/solrcloud-shar
did you solve this eventually?
Aditya Sakhuja wrote
> 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 p
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:*
>
> Cannot successfully resto
Hi,
Sorry for the late followup on this. Let me put in more details here.
*The problem:*
Cannot successfully restore back the index backed up with
'/replication?command=backup'. The backup was generated as *
snapshot.mmdd*
*My setup and steps:*
*
*
6 solrcloud instances
7 zookeepers instanc
I wouldn't say I love this idea, but wouldn't it be safe to LVM snapshot
the Solr index? I think this may even work on a live server, depending on
some file I/O details. Has anyone tried this?
An in-Solr solution sounds more elegant, but considering the tlog concern
Shalin mentioned, I think this
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 of the index. Lets say we have 3 shards across 3 solrcloud
servers.
1.> I am assuming we should take a backup from each of the shard leaders t
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 wrote:
> I don't know that it's too bad though - its always been the case that if you
> do a backup while indexin
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
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
11 matches
Mail list logo
