[ https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611757#comment-14611757 ]
Noble Paul commented on SOLR-5750: ---------------------------------- 2 design suggestions 1) Move the operations to {{CollectionsHandler}} . When the process starts add the backup name and the node that is processing the task to ZK 2) Do not restore all the replicas at once . Just create one replica of a shard first and then do ADDREPLICA till you have enough replicas > 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 > > > 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