[
https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3630:
-----------------------------
Description:
Currently, one rocksdb for one container. one container has 5GB capacity. 10TB
data need more than 2000 rocksdb in one datanode. It's difficult to limit the
memory of 2000 rocksdb. So maybe we should limited instance of rocksdb for each
disk.
The design of improvement is in the follow link, but still is a draft.
TODO:
1. compatibility with current logic i.e. one rocksdb for each container
2. measure the memory usage before and after improvement
3. effect on efficiency of read and write.
https://docs.google.com/document/d/18Ybg-NjyU602c-MYXaJHP6yrg-dVMZKGyoK5C_pp1mM/edit#
was:
Currently, one rocksdb for one container. one container has 5GB capacity. 10TB
data need more than 2000 rocksdb in one datanode. It's difficult to limit the
memory of 2000 rocksdb. So maybe we should limited instance of rocksdb for each
disk.
The design of improvement is in the follow link, but still is a draft.
TODO:
1. measure the memory usage before and after improvement
2. compatibility with current logic i.e. one rocksdb for each container
3. effect on efficiency of read and write.
https://docs.google.com/document/d/18Ybg-NjyU602c-MYXaJHP6yrg-dVMZKGyoK5C_pp1mM/edit#
> Merge rocksdb in datanode
> -------------------------
>
> Key: HDDS-3630
> URL: https://issues.apache.org/jira/browse/HDDS-3630
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: runzhiwang
> Assignee: runzhiwang
> Priority: Major
> Attachments: Merge RocksDB in Datanode.pdf
>
>
> Currently, one rocksdb for one container. one container has 5GB capacity.
> 10TB data need more than 2000 rocksdb in one datanode. It's difficult to
> limit the memory of 2000 rocksdb. So maybe we should limited instance of
> rocksdb for each disk.
> The design of improvement is in the follow link, but still is a draft.
> TODO:
> 1. compatibility with current logic i.e. one rocksdb for each container
> 2. measure the memory usage before and after improvement
> 3. effect on efficiency of read and write.
> https://docs.google.com/document/d/18Ybg-NjyU602c-MYXaJHP6yrg-dVMZKGyoK5C_pp1mM/edit#
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
