[
https://issues.apache.org/jira/browse/HDFS-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024858#comment-17024858
]
maobaolong commented on HDFS-15133:
-----------------------------------
[~brahmareddy] [~ayushtkn], After some work these day, i give some update now.
- I copy the package `org.apache.hadoop.hdds.utils.db` from hadoop-ozone
project to the package `org.apache.hadoop.hdds.utils.db` of the module
hadoop-common of the project hadoop. In fact i think i have done the sub task
HDFS-15137
- I'm doing a refactor for INodeMap, i try to abstract the `GSet<INode,
INodeWithAdditionalFields> map` into a concept named `InodeStore`.
It have two implementation, one named HeapInodeStore, as the name, it is the
origin mode, the other named RocksInodeStore, it work as rocksdb mode. In fact,
i'm doing the part of https://issues.apache.org/jira/browse/HDFS-15138.
But, i met some problem,
- It is hard to measure the size of a rocksdb?
- how to implements the method getMapIterator graceful for the RocksInodeStore.
- Clear method will be implements to reset the rocksdb for the RocksInodeStore.
Future Job
- I will commit my work to my branch named rocks-metastore, my repo is
https://github.com/maobaolong/hadoop. As now, it contains compile error now, so
i will commit several days later.
- Feel free to discuss with my here or in the slack hdfs channel
- Feel free to take these jira task or help me to correct my mistake
- Doing some minor test.
> 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]