[
https://issues.apache.org/jira/browse/HDFS-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033008#comment-17033008
]
Ayush Saxena commented on HDFS-15133:
-------------------------------------
bq. 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
Are you talking about {{INodeDirectory rootDir;}} in FSDirectory? If so,
Presently it stores root as {{InodeDirectory}} we can change to just the inode
Id of the root and whenever the root is required we can fetch it using the
root's inode Id from the inode map. The rootDir is also put into InodeMap.
[~maobaolong] regarding the whole of Inodes in the DB, I have a doubt on this
if you put all of the nodes into DB, if you fetch a entry from DB and then do
modifications on it. I think we need to replace the updated Inode in the DB,
which was not done when the Inode object stayed in heap.
Each inode contains reference to parent and its children, When in heap, its all
references, if you add one child it can be chained from the top most Inode, now
to add a INode, do we need to update all the parent entries?
> 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]
