You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "runzhiwang (Jira)" <ji...@apache.org> on 2020/10/23 01:33:00 UTC
[jira] [Updated] (HDDS-4383) Datanode truncates blocks on the disk
[ https://issues.apache.org/jira/browse/HDDS-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
runzhiwang updated HDDS-4383:
-----------------------------
Description: Datanode starts a background thread to process <TRUNCATING_blockID, newLength>. If it is FilePerBlock, we use FileChannel.truncate to truncate file to newLength directly. If it is FilePerChunk, we delete the files of the fully truncated chunks, and use FileChannel.truncate to process the partially truncated file. Then, in RocksDB, Datanode delete <TRUNCATING_blockid, newLength>, and put <TRUNCATED_blockid, newLength>.
> Datanode truncates blocks on the disk
> -------------------------------------
>
> Key: HDDS-4383
> URL: https://issues.apache.org/jira/browse/HDDS-4383
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: runzhiwang
> Priority: Major
>
> Datanode starts a background thread to process <TRUNCATING_blockID, newLength>. If it is FilePerBlock, we use FileChannel.truncate to truncate file to newLength directly. If it is FilePerChunk, we delete the files of the fully truncated chunks, and use FileChannel.truncate to process the partially truncated file. Then, in RocksDB, Datanode delete <TRUNCATING_blockid, newLength>, and put <TRUNCATED_blockid, newLength>.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org