[
https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126396#comment-15126396
]
David Smiley commented on SOLR-5750:
------------------------------------
What's left to do on this issue? Does it actually work? The feedback I've
seen seem to be around improvements to make it better -- i.e. using a shared
filesystem resulting in no actual copying of files.
I looked at the patch. On the restore side I noticed a loop of slices and then
a loop of replicas starting with this comment: "//Copy data from backed up
index to each replica". Shouldn't there be just one replica per shard to
restore, and then later the replicationFactor will expand to the desired level?
Another question is I wonder if any of these loops should be done in parallel
or if they are issuing asynchronous requests so it isn't necessary. It would
help to document the pertinent loops with this information, and possibly do
some in parallel if they should be done so.
> Backup/Restore API for SolrCloud
> --------------------------------
>
> Key: SOLR-5750
> URL: https://issues.apache.org/jira/browse/SOLR-5750
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Varun Thacker
> Fix For: 5.2, Trunk
>
> Attachments: SOLR-5750.patch, SOLR-5750.patch, SOLR-5750.patch,
> SOLR-5750.patch
>
>
> We should have an easy way to do backups and restores in SolrCloud. The
> ReplicationHandler supports a backup command which can create snapshots of
> the index but that is too little.
> The command should be able to backup:
> # Snapshots of all indexes or indexes from the leader or the shards
> # Config set
> # Cluster state
> # Cluster properties
> # Aliases
> # Overseer work queue?
> A restore should be able to completely restore the cloud i.e. no manual steps
> required other than bringing nodes back up or setting up a new cloud cluster.
> SOLR-5340 will be a part of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
