[ 
https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240649#comment-15240649
 ] 

David Smiley commented on SOLR-5750:
------------------------------------

I pushed some new commits to the branch: 
https://github.com/apache/lucene-solr/commits/solr-5750
Some important bits:
* Restored conf name is configurable; won't overwrite existing. Defaults to 
original.
* replicationFactor and some other settings are customizable on restoration.
* Shard/slice info is restored instead of reconstituted.  Thus shard hash 
ranges (from e.g. shard split) is restored.

I still want to:
* test asyncId
* test property.customKey=customVal passes through
* resolve nocommits on how to pass config name & replicationFactor on the SolrJ 
side

Beyond that there are just some nocommits of a cleanup/document nature.  I code 
review would be much appreciated.  Should we just use GitHub branches (do I 
need my own fork?) for that or ReviewBoard?

Possibly in this issue but more likely in another, it would be great if 
collection restoration could honor CREATE_NODE_SET, snitches, and rules.  I 
need to see how much extra work that'd be but I don't want to delay this too 
much.

> 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

Reply via email to