You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2020/04/28 11:46:00 UTC
[jira] [Commented] (HDDS-3499) Address compatibility issue by SCM
DB instances change
[ https://issues.apache.org/jira/browse/HDDS-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094429#comment-17094429 ]
Marton Elek commented on HDDS-3499:
-----------------------------------
I am checking the native rocksdb tools if they are usable. As the structure is not changes, it can be possible to migrate column family from one db to an other...
> Address compatibility issue by SCM DB instances change
> ------------------------------------------------------
>
> Key: HDDS-3499
> URL: https://issues.apache.org/jira/browse/HDDS-3499
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Li Cheng
> Priority: Blocker
>
> After https://issues.apache.org/jira/browse/HDDS-3172, SCM now has one single rocksdb instance instead of multiple db instances.
> For running Ozone cluster, we need to address compatibility issues. One possible way is to have a side-way tool to migrate old metadata from multiple dbs to current single db.
--
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