[
https://issues.apache.org/jira/browse/SOLR-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014898#comment-15014898
]
Varun Thacker commented on SOLR-5750:
-------------------------------------
bq. 1) I know we already have "location" via
https://cwiki.apache.org/confluence/display/solr/Making+and+Restoring+Backups+of+SolrCores
but it just seems needlessly risky / error prone. What if a user purposefully
or accidentally overwrites important data? You are giving anyone making a
snapshot call solr's permissions. Beyond that, making "location" a required
param is not the greatest interface. Most of the time when I'm taking a
snapshot I don't even care where it is, I expect the system to just do
something sensible and let me interact with the API with some id (i.e. name).
HDFS and HBase snapshots work in this way, for example. Why not just have a
backup location specified in solr.xml with some sensible default?
bq. 2) On the above point: "I expect the system to just do something sensible
and let me interact with the API with some id (i.e. name)" – why do I pass in a
location for RESTORE? Can't the system just remember that from the backup call?
Nice idea. We could let users specify it within the solr.xml solrcloud tag .
I don't think it should default to anything and if not specified snapshots
should fail. The reason being users not on a shared filesystem need to specify
a shared mount for this to work.
And by specifying it within the solr.xml file , even the restore command
wouldn't need the user to specify the location which will solve your concern in
the 2nd point
{code}
<solr>
<solrcloud>
<str name="snapshotDirectory">${snapshotDirectory:}</str> <!-- the path
specified here should be a shared mount accessible by all nodes in the cluster
for backup/restore to work on non shared file systems -->
</solrcloud>
</solr>
{code}
> 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,
> 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: [email protected]
For additional commands, e-mail: [email protected]
