[
https://issues.apache.org/jira/browse/HDDS-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
UENISHI Kota updated HDDS-5893:
-------------------------------
Description:
In case mutlipart upload completion with unused parts, and the key is not first
created (some previous versions in deletion table), 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.
was:
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.
> 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
> Assignee: UENISHI Kota
> Priority: Critical
> Labels: pull-request-available
>
> In case mutlipart upload completion with unused parts, and the key is not
> first created (some previous versions in deletion table), 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: [email protected]
For additional commands, e-mail: [email protected]
