[
https://issues.apache.org/jira/browse/HDFS-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020727#comment-17020727
]
maobaolong commented on HDFS-15133:
-----------------------------------
[~iwasakims] [~hemanthboyina] After review the HDFS-5389 and HDFS-8286, i saw
the similar design, but they are all aimed to invent a new approach to achieve
the goal. This jira mainly hope to reuse the approach of how to manage racksdb
which implemented in HDDS.
The RDBStore and TypedTable can be responsible for the kv store manager, so we
can starts all work by the moving the code of RDBStore related to
hadoop-common, so that ozone and hdfs or yarn and other component can use this
wonderful feature without any more effort.
> Use rocksdb to store NameNode inode and blockInfo
> -------------------------------------------------
>
> Key: HDFS-15133
> URL: https://issues.apache.org/jira/browse/HDFS-15133
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.3.0
> Reporter: maobaolong
> Priority: Major
>
> Maybe we don't need checkpoint to a fsimage file, the rocksdb checkpoint can
> achieve the same request.
> This is ozone and alluxio way to manage meta data of master node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
