You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/10/25 00:24:00 UTC
[jira] [Updated] (HDDS-5893) Potential data loss on multipart
upload commit
[ https://issues.apache.org/jira/browse/HDDS-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-5893:
---------------------------------
Labels: pull-request-available (was: )
> Potential data loss on multipart upload commit
> ----------------------------------------------
>
> Key: HDDS-5893
> URL: https://issues.apache.org/jira/browse/HDDS-5893
> Project: Apache Ozone
> Issue Type: Bug
> Components: OM
> Affects Versions: 0.5.0, 1.0.0, 1.1.0
> Reporter: UENISHI Kota
> Priority: Critical
> Labels: pull-request-available
>
> In case mutlipart upload completion with unused parts, and the key is first created (no previous version), the committed live version of OmKeyInfo is added to deletion table. The key will be live until the deletion service collects the blocks, but after blocks deleted, the key metadata will be visible from user API while the blocks are already deleted.
> This potential bug has been resident since HDDS-2395, as long as I searched the Git history. (I have just found this issue during the code review, so I have not yet reproduced manually and I may miss other code.) I'll post an instant patch later.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org