You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hrishikesh Gadre (JIRA)" <ji...@apache.org> on 2016/03/31 20:35:25 UTC
[jira] [Comment Edited] (SOLR-5750) Backup/Restore API for
SolrCloud
[ https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220368#comment-15220368 ]
Hrishikesh Gadre edited comment on SOLR-5750 at 3/31/16 6:35 PM:
-----------------------------------------------------------------
[~varunthacker] Thanks for the info. That make sense.
I am currently investigating Solr Backup/restore changes for HDFS. I found this old email thread which discusses different approaches,
http://qnalist.com/questions/5433155/proper-way-to-backup-solr
I think we settled on "copying" behavior for portability reason. I think we should make this a configurable behavior so that we can make the best use of capabilities of underlying file-system. May be we introduce a higher level API? I think the API should consider source and destination file-systems to figure out the "correct" and "optimized" behavior...
Any thoughts?
CC [~elyograg] [~markrmiller@gmail.com] [~yonik@apache.org]
was (Author: hgadre):
[~varunthacker] Thanks for the info. That make sense.
I am currently investigating Solr Backup/restore changes for HDFS. I found this old email thread which discusses different approaches,
http://qnalist.com/questions/5433155/proper-way-to-backup-solr
I think we settled on "copying" behavior for portability reason. I think we should make this a configurable behavior so that we can make the best use of capabilities of underlying file-system. May be we introduce a higher level API (may be at the Directory interface level) ?
Any thoughts?
CC [~elyograg] [~markrmiller@gmail.com] [~yonik@apache.org]
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org