[
https://issues.apache.org/jira/browse/SOLR-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262556#comment-15262556
]
David Smiley commented on SOLR-9038:
------------------------------------
bq. >>I presume by "snapshot", we're talking about named (or numbered) Lucene
IndexCommit objects across all replicas of a Solr Collection? And then, in
SOLR-5750 or future patch, the "backup" capability might optionally make
reference to a named snapshot instead of just taking the last IndexCommit?
bq. Yes that is correct.
Yet I'm now unsure we're actually talking about the same thing, given
everything else you've said. If this issue you propose is anything more than
adding commit metadata (copying segments to another place _is_ more than just
adding commit metadata), then how is this issue different then SOLR-5750? I
understand we want to leverage storage level efficiencies (e.g. distcp) but
this issue doesn't seem to actually be about that. Its appearing to be
redundant with SOLR-5750. Or perhaps you mean, extend/enhance the result of
SOLR-5750 so that we have an API to list & delete the backups without requiring
a client to go to the shared file system to observe what backups there are?
Big +1 to that and if so please clarify the title/description and add a
requires linkage to SOLR-5750. Again if you mean that, then mentioning HDFS
etc. is a distraction to this issue's purpose.
> Ability to create/delete/list snapshots for a solr collection
> -------------------------------------------------------------
>
> Key: SOLR-9038
> URL: https://issues.apache.org/jira/browse/SOLR-9038
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Hrishikesh Gadre
>
> Currently work is under-way to implement backup/restore API for Solr cloud
> (SOLR-5750). SOLR-5750 is about providing an ability to "copy" index files
> and collection metadata to a configurable location.
> In addition to this, we should also provide a facility to create "named"
> snapshots for Solr collection. Here by "snapshot" I mean configuring the
> underlying Lucene IndexDeletionPolicy to not delete a specific commit point
> (e.g. using PersistentSnapshotIndexDeletionPolicy). This should not be
> confused with SOLR-5340 which implements core level "backup" functionality.
> The primary motivation of this feature is to decouple recording/preserving a
> known consistent state of a collection from actually "copying" the relevant
> files to a physically separate location. This decoupling have number of
> advantages
> - We can use specialized data-copying tools for transferring Solr index
> files. e.g. in Hadoop environment, typically
> [distcp|https://hadoop.apache.org/docs/r1.2.1/distcp2.html] tool is used to
> copy files from one location to other. This tool provides various options to
> configure degree of parallelism, bandwidth usage as well as integration with
> different types and versions of file systems (e.g. AWS S3, Azure Blob store
> etc.)
> - This separation of concern would also help Solr to focus on the key
> functionality (i.e. querying and indexing) while delegating the copy
> operation to the tools built for that purpose.
> - Users can decide if/when to copy the data files as against creating a
> snapshot. e.g. a user may want to create a snapshot of a collection before
> making an experimental change (e.g. updating/deleting docs, schema change
> etc.). If the experiment is successful, he can delete the snapshot (without
> having to copy the files). If the experiment is failed, then he can copy the
> files associated with the snapshot and restore.
> Note that Apache Blur project is also providing a similar feature
> [BLUR-132|https://issues.apache.org/jira/browse/BLUR-132]
--
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
