[ https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264704#comment-15264704 ]
Hrishikesh Gadre commented on SOLR-5750: ---------------------------------------- [~dsmiley] I am almost done with refactoring the patch. I will submit the patch in next couple of hours. >>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. I have already fixed this in my patch. > 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