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 "Andrei Dulceanu (Jira)" <ji...@apache.org> on 2023/04/14 14:54:00 UTC

[jira] [Updated] (OAK-10190) Reusing Azure segment container hangs when primary location is not available

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

Andrei Dulceanu updated OAK-10190:
----------------------------------
    Issue Type: Bug  (was: Task)

> Reusing Azure segment container hangs when primary location is not available
> ----------------------------------------------------------------------------
>
>                 Key: OAK-10190
>                 URL: https://issues.apache.org/jira/browse/OAK-10190
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-azure
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Major
>
> When access to the secondary Azure blobstore service endpoint in Oak segment node store is enabled (see OAK-10050), re-using the Azure segment container hangs if the primary location is not available.
> This happens because the call {{container.createIfNotExists()}} always overrides the request options set and goes to primary location only, since that is the only one allowing write access (in case the container needs to be created).



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