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 2023/11/21 13:14:00 UTC

[jira] [Updated] (OAK-10006) AzurePersistence can still write segments after having lost lease to another instance

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

Miroslav Smiljanic updated OAK-10006:
-------------------------------------
    Affects Version/s: 1.58.0

> AzurePersistence can still write segments after having lost lease to another instance
> -------------------------------------------------------------------------------------
>
>                 Key: OAK-10006
>                 URL: https://issues.apache.org/jira/browse/OAK-10006
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-azure, segment-tar
>    Affects Versions: 1.44.0, 1.58.0
>            Reporter: Carlo Jelmini
>            Assignee: Miroslav Smiljanic
>            Priority: Major
>             Fix For: 1.60.0
>
>
> If the SegmentWriteQueue have pending writes while AzurePersistence is unable to renew the lease (both likely caused by connection problems with Azure), and another Oak instance starts and acquire the lease, then the first Oak instance may still be able to write segments to Azure, corrupting the repository.
> We need to make sure no writes can happen if the lease has been lost to another instance.



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