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 2021/01/21 12:42:10 UTC
[jira] [Updated] (OAK-9212) AzureArchiveManage.listArchives()
should not delete segments
[ https://issues.apache.org/jira/browse/OAK-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dulceanu updated OAK-9212:
---------------------------------
Fix Version/s: (was: 1.38.0)
1.40.0
> AzureArchiveManage.listArchives() should not delete segments
> ------------------------------------------------------------
>
> Key: OAK-9212
> URL: https://issues.apache.org/jira/browse/OAK-9212
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-azure
> Affects Versions: 1.32.0
> Reporter: Aravindo Wingeier
> Priority: Major
> Fix For: 1.40.0
>
>
> When the segments are listed on an azure blob store and the "0000.*" blob is missing, it will delete all other segments. This behaviour was introduced with OAK-8566.
> *Change:* This destructive operation should not happen in method the _AzureArchiveManage.listArchives()_ which indicates a read-only operation. One option is to pull out this functionality and call it somewhere else.
> *Why is this an issue?* There is a recovery option in org.apache.jackrabbit.oak.segment.file.tar.TarReader#collectFileEntries which calls org.apache.jackrabbit.oak.segment.file.tar.TarReader#backupSafely. If the recovery is run concurrently with _AzureArchiveManage.listArchives()_ the result can be unexpected.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)