You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/05/07 02:50:00 UTC

[jira] [Updated] (HDDS-6556) Update usedBytes only when commit key.

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

mingchao zhao updated HDDS-6556:
--------------------------------
    Affects Version/s: 1.2.0

> Update usedBytes only when commit key.
> --------------------------------------
>
>                 Key: HDDS-6556
>                 URL: https://issues.apache.org/jira/browse/HDDS-6556
>             Project: Apache Ozone
>          Issue Type: Sub-task
>    Affects Versions: 1.2.0
>            Reporter: mingchao zhao
>            Assignee: mingchao zhao
>            Priority: Major
>              Labels: pull-request-available
>
> As we disscussed in https://issues.apache.org/jira/browse/HDDS-5867.
> The quota we are currently implementing have a bug. When allocate block, we add usedBytes. If the key fails to write, the Clean Open Key Service subtracts the usedBytes. But the bucket may no longer exist when the open key is being deleted, or may have been deleted and re-created with the same name.  This causes usedBytes update error.
> We can only update the usedByte when commit key. In this way, failed keys are not counted in the usedByte(we‘ll add service in the background to delete them). This is reasonable for the user. This is garbage data and belongs to the Ozone system. And the Ozone system itself cleans this data.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org