[ 
https://issues.apache.org/jira/browse/HDDS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shashikant Banerjee resolved HDDS-3244.
---------------------------------------
    Fix Version/s: 0.6.0
       Resolution: Fixed

Thanks [~yjxxtd] for working on this. I have committed this.

> Improve write efficiency by opening RocksDB only once
> -----------------------------------------------------
>
>                 Key: HDDS-3244
>                 URL: https://issues.apache.org/jira/browse/HDDS-3244
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: runzhiwang
>            Assignee: runzhiwang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.6.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> when datanode create each container, a new RocksDB instance will be 
> [created|https://github.com/apache/hadoop-ozone/blob/master/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/keyvalue/helpers/KeyValueContainerUtil.java#L76],
>  but then the created RocksDB was 
> [closed|https://github.com/apache/hadoop-ozone/blob/master/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/keyvalue/helpers/KeyValueContainerUtil.java#L83],
>  until PutBlock the RocsDB will be 
> [opend|https://github.com/apache/hadoop-ozone/blob/master/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/utils/ContainerCache.java#L123]
>  again, so the RocksDB was open twice.  
> [RocksDB.open|https://github.com/apache/hadoop-ozone/blob/master/hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/utils/RocksDBStore.java#L68]
>  cost about 150ms-200ms,  it's  a waste to open it twice.
>   I will try to open the RocksDB only once.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to