[
https://issues.apache.org/jira/browse/HDFS-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025528#comment-17025528
]
maobaolong commented on HDFS-15133:
-----------------------------------
[~hemanthboyina] Thank you for your question.
Indeed, if the RocksInodeStore works perfect, it is no need to have a
HeapInodeStore, but everything has two sides, although rocksInodeStore mode can
enlarge the maximum of inode, and we will try to use cache to improve the
performance, but i think in some scenarios, HeapInodeStore can work well, and i
think some company use the origin heap mode well, they don't have to try the
rocksInodeStore, so we must provide a way to let them run the namenode in the
origin way. HeapInodeStore is the origin way to manage inode.
> 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
> Attachments: image-2020-01-28-12-30-33-015.png
>
>
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
