You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/26 19:08:00 UTC

[jira] [Commented] (HDDS-3869) Use different column families for datanode block and metadata

    [ https://issues.apache.org/jira/browse/HDDS-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146583#comment-17146583 ] 

Arpit Agarwal commented on HDDS-3869:
-------------------------------------

I am removing the backward incompatible label since we can mitigate this via auto-migration.

> Use different column families for datanode block and metadata
> -------------------------------------------------------------
>
>                 Key: HDDS-3869
>                 URL: https://issues.apache.org/jira/browse/HDDS-3869
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Ethan Rose
>            Assignee: Ethan Rose
>            Priority: Critical
>              Labels: upgrade
>
> Currently datanodes place all of their data under the default column family in RocksDB. This differs from OM and SCM which organize their data into different column families based on its type. By having the datanode place its metadata in one column family, and block data in another, it will be easier to view for debugging and organizational purposes.



--
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