[
https://issues.apache.org/jira/browse/HDDS-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-10379:
------------------------------
Summary: Datanodes should generate initial container merkle tree during
container close (was: Datanode will generate Merkle Tree as part of container
close)
> Datanodes should generate initial container merkle tree during container close
> ------------------------------------------------------------------------------
>
> Key: HDDS-10379
> URL: https://issues.apache.org/jira/browse/HDDS-10379
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ritesh Shukla
> Priority: Major
>
> Open container replicas will not have a container merkle tree so that we do
> not need to keep updating this with every write request. Instead, the tree
> will be created on container close from the chunk checksums that are stored
> in RocksDB. Since these checksums should have been verified somewhat recently
> (with write checksum verification enabled), container close will build the
> merkle tree from these values without reading actual data blocks. Since
> should just be a hash of values stored contiguously in RocksDB, it should be
> a fast operation. The container scanner will come back asynchronously to
> update update the checksums based on the data it sees on disk at that time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
