Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
In HDDS-10376, the API to read a container's merkle tree was implemented without zero-copy. This should be ok for phase 1 where reconciliation is only triggered manually. However, we should avoid the extra copy of the file's data before reconciliation is automated and calls to the API increase in frequency.
Attachments
Issue Links
- relates to
-
HDDS-10144 Zero-Copy in replication
- Resolved
- split from
-
HDDS-10376 Add a Datanode API to supply a merkle tree for a given container
- Resolved