You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Miroslav Smiljanic (Jira)" <ji...@apache.org> on 2022/08/31 09:31:00 UTC

[jira] [Assigned] (OAK-9914) Starting Oak with Azure persistence in read-only mode while another Oak process is running will initiate repo recovery

     [ https://issues.apache.org/jira/browse/OAK-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miroslav Smiljanic reassigned OAK-9914:
---------------------------------------

    Assignee: Miroslav Smiljanic

> Starting Oak with Azure persistence in read-only mode while another Oak process is running will initiate repo recovery
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: OAK-9914
>                 URL: https://issues.apache.org/jira/browse/OAK-9914
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: segment-azure
>    Affects Versions: 1.44.0
>            Reporter: Miroslav Smiljanic
>            Assignee: Miroslav Smiljanic
>            Priority: Major
>         Attachments: AzureArchiveManager.patch, OAK-9914_test.patch
>
>
> The sequence of events:
>  # Oak process with read/write file store utilizing Azure persistence is already running 
>  # New Oak process is starting up, with read-only file store using Azure persistence and the same storage account and container like the previous Oak process
>  ## New Oak process starts recovery procedure for the last tar directory that is not closed
> Scenario presented in the attached test case:
> [^OAK-9914_test.patch] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)