[
https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264676#comment-15264676
]
David Smiley commented on SOLR-5750:
------------------------------------
I'll give some more time for review, like maybe Monday unless there are further
changes to be done from any review/feedback. Some things I think I want to
change (which I will do today):
* simply remove the Overseer.processMessage case statements for RESTORE &
BACKUP as they simply aren't used. This resolves a nocommit.
* to avoid risk of confusion with "snapshot" possibly being a named commit
(SOLR-9038) in the log statements and backup.properites I'll call it a
backupName, not snapshotName.
Tentative CHANGES.txt is as follows:
{noformat}
* SOLR-5750: Add /admin/collections?action=BACKUP and RESTORE assuming access
to a shared file system.
(Varun Thacker, David Smiley)
{noformat}
About the "shared file system" requirement, it occurred to me this isn't really
tested; it'd be nice it if failed fast if not all shards can see the backup
location's ZK backup export. I'm working on ensuring the backup fails if all
slices don't see the backup directory that should be created at the start of
the backup process. This seems a small matter of ensuring that
SnapShooter.validateCreateSnapshot call mkdir (which will fail if the parent
dir isn't there) and not mkdirs but I'm testing to ensure the replication
handler's use of SnapShooter is fine with this; I think it is.
> 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: David Smiley
> Fix For: 5.2, master
>
> Attachments: SOLR-5750.patch, SOLR-5750.patch, SOLR-5750.patch,
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
