[jira] [Updated] (HDDS-8117) Move block files to container directory after the first put block

["Ethan Rose (Jira)" <ji...@apache.org>]

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

Ethan Rose updated HDDS-8117:
-----------------------------
    Parent Issue: HDDS-8161  (was: HDDS-6548)

> Move block files to container directory after the first put block
> -----------------------------------------------------------------
>
>                 Key: HDDS-8117
>                 URL: https://issues.apache.org/jira/browse/HDDS-8117
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ritesh Shukla
>            Priority: Major
>
> If there is a failure in the write chunk requests before the first put block, a file will be left in the container directory that has no corresponding RocksDB entry. This isn't really a bug because the data is unreferenced, but it would be good to have the container directory only contain block files with committed data.
> The proposal is to initially write the block file to a tmp directory, and use atomic filesystem mv to put it in the container directory on the first put block request. Subsequent writes to the block will use the block file in the container.



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

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