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

Mark Gui updated HDDS-6544:
---------------------------
    Description: 
After rocksdb merge, all container metadata all resides in a single db 
instance, so we can't just export the container by tar the container directory 
into a tarball and send it over, we have to extract the metadata that belong to 
the container to be replicated and include them in the tarball. After the 
target DN received the tarball, it should pay attention to import those 
metadata files into the local db instance.

Rocksdb provides facilities to dump and import range KVs with sst files:
 * SstFileWriter
 * ingestExternalFile

FYI: https://github.com/facebook/rocksdb/wiki/Creating-and-Ingesting-SST-files

> New container replication operations for schema v3 container.
> -------------------------------------------------------------
>
>                 Key: HDDS-6544
>                 URL: https://issues.apache.org/jira/browse/HDDS-6544
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Mark Gui
>            Assignee: Mark Gui
>            Priority: Major
>
> After rocksdb merge, all container metadata all resides in a single db 
> instance, so we can't just export the container by tar the container 
> directory into a tarball and send it over, we have to extract the metadata 
> that belong to the container to be replicated and include them in the 
> tarball. After the target DN received the tarball, it should pay attention to 
> import those metadata files into the local db instance.
> Rocksdb provides facilities to dump and import range KVs with sst files:
>  * SstFileWriter
>  * ingestExternalFile
> FYI: https://github.com/facebook/rocksdb/wiki/Creating-and-Ingesting-SST-files



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to