Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-15086 SIP-12 Implementation Umbrella
  3. SOLR-15089

Allow backup/restoration to Amazon's S3 blobstore

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Implemented
    • None
    • 8.10
    • None

    Description

      Solr's BackupRepository interface provides an abstraction around the physical location/format that backups are stored in. This allows plugin writers to create "repositories" for a variety of storage mediums. It'd be nice if Solr offered more mediums out of the box though, such as some of the "blobstore" offerings provided by various cloud providers.

      This ticket proposes that a "BackupRepository" implementation for Amazon's popular 'S3' blobstore, so that Solr users can use it for backups without needing to write their own code.

      Amazon offers a s3 Java client with acceptable licensing, and the required code is relatively simple. The biggest challenge in supporting this will likely be procedural - integration testing requires S3 access and S3 access costs money. We can check with INFRA to see if there is any way to get cloud credits for an integration test to run in nightly Jenkins runs on the ASF Jenkins server. Alternatively we can try to stub out the blobstore in some reliable way.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            houston Houston Putman
            gerlowskija Jason Gerlowski
            Votes:
            3 Vote for this issue
            Watchers:
            19 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 14h 40m
              14h 40m

              Slack

                Issue deployment