Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-7735

Split segment store persistence

    XMLWordPrintableJSON

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.10.0, 1.9.9
    • Component/s: segment-tar
    • Labels:
      None

      Description

      Split segment store persistence is a proxy layer that can be used between the SegmentMK and the actual segment store persistence. It's configured with two backends: read-only and read-write. It delegates all the read requests to the read-only backend, but any write request (eg. creating a new segment) is delegated to the read-write backend.

      The main advantage is that we can have a segment store in the cloud (using the oak-segment-azure), shared amongst many Oak instances, starting dynamically. All the changes specific for a given instance are stored locally, with the TarPersistence.

      The implementation remembers the state (tar file list, last journal entry) of the read-only backend during it's initialisation, so the read-only backend can be used by a different instance, as long as it only appends new segments (eg. no compaction).

        Attachments

        1. OAK-7735.patch
          22 kB
          Tomek Rękawek

          Activity

            People

            • Assignee:
              tomek.rekawek Tomek Rękawek
              Reporter:
              tomek.rekawek Tomek Rękawek
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: