[
https://issues.apache.org/jira/browse/HDFS-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032990#comment-17032990
]
hemanthboyina commented on HDFS-15133:
--------------------------------------
thanks for the work [~maobaolong]
{quote}We propose to implement the HDFS namespace on top of a key-value (KV)
store
{quote}
IMO Storing the INode into RocksDB doesn't satisfy our problem scenario , as in
the existing HDFS code we have a tree structure of INode's in Heap which will
be put in INodeMap and used as reference
To solve our problem scenario we are proposing to have a light weight INode
which will be having variables ID and name only , so the size of light weight
INode object will be very less comparing to existing INode
After this modification , light weight INode object will be in Heap and
Complete INode object in RocksDB
I have created HDFS-15152 to implement this
> 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: [email protected]
For additional commands, e-mail: [email protected]
