[ https://issues.apache.org/jira/browse/OAK-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomek Rękawek resolved OAK-7735. -------------------------------- Resolution: Fixed > Split segment store persistence > ------------------------------- > > Key: OAK-7735 > URL: https://issues.apache.org/jira/browse/OAK-7735 > Project: Jackrabbit Oak > Issue Type: Story > Components: segment-tar > Reporter: Tomek Rękawek > Assignee: Tomek Rękawek > Priority: Major > Fix For: 1.10, 1.9.9 > > Attachments: OAK-7735.patch > > > 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). -- This message was sent by Atlassian JIRA (v7.6.3#76005)