ChenSammi commented on code in PR #7807: URL: https://github.com/apache/ozone/pull/7807#discussion_r1942496603
########## hadoop-hdds/docs/content/feature/dn-merge-rocksdb.md: ########## @@ -27,7 +27,8 @@ In Ozone, user data are separated into blocks and stored in HDDS Containers. Con Earlier, there was one RocksDB for each Container on datanode. With user data continously growing, there will be hundreds of thousands of RocksDB instances on one datanode. It's a big challenge to manage this amount of RocksDB instances in one JVM. -Unlike the previous approach, this "Merge Container RocksDB in DN" feature will use only one RocksDB for each data volume, holding all metadata of Containers in this RocksDB. +Unlike the previous approach, this "Merge Container RocksDB in DN" feature will use only one RocksDB for each data volume +(here, data volume means the disc volume and not the ozone metadata volume) holding all metadata of Containers in this RocksDB. Review Comment: @Gargi-jais11, thanks for raising the question. "data volume" in Ozone context means the directories defined with "hdds.datanode.dir" which are used to save Ozone container data. Besides "data volume", there are "metadata volume" which are used to save ratis logs. I think these two concepts are well received by Ozone users. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
