[ https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219645#comment-15219645 ]
Jan Høydahl commented on SOLR-5750: ----------------------------------- bq. Creates a core-less collection with the config set from the backup ( it appends a restore.configSetName to it for avoiding collissions ) What if we backup two collections using the same config "foo"? After restore of the first collection, we will have a config "restore.foo", but what happens during restore of the second collection? Have not looked at the patch code. Should it not be a goal that a backup + nuke + restore leaves you with a state as close to the original as possible, i.e. with one config called "foo", used by both collections? Perhaps a restore option {{shareConfig=true}} which creates the config if missing, otherwise reuses what is there? > 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, master > > Attachments: 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