[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-----------------------------
Description:
As the image shows, when write data, the leader datanode execute two steps:
KeyValueHandleHandler.handleCreateContainer, keyValueHandler.handleWriteChunk,
after leader finish the two steps, the two follower datanodes execute two
steps: KeyValueHandleHandler.handleCreateContainer,
keyValueHandler.handleWriteChunk.
The problem is KeyValueHandleHandler.handleCreateContainer cost about 300ms, so
the leader and two followers cost 600ms to createContainer, it's a waste.
Besides, when createContainer, RocksDB.open cost about 200ms.
So I will try to:
1. leader datanode and 2 follower datanodes create container in parallel, not
in sequential.
2. optimize RocksDB.open.
!screenshot-1.png!
was:
!screenshot-1.png!
> Improve write efficiency by creating container parallel.
> --------------------------------------------------------
>
> Key: HDDS-3240
> URL: https://issues.apache.org/jira/browse/HDDS-3240
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: runzhiwang
> Assignee: runzhiwang
> Priority: Major
> Attachments: screenshot-1.png
>
>
> As the image shows, when write data, the leader datanode execute two steps:
> KeyValueHandleHandler.handleCreateContainer,
> keyValueHandler.handleWriteChunk, after leader finish the two steps, the two
> follower datanodes execute two steps:
> KeyValueHandleHandler.handleCreateContainer,
> keyValueHandler.handleWriteChunk.
> The problem is KeyValueHandleHandler.handleCreateContainer cost about 300ms,
> so the leader and two followers cost 600ms to createContainer, it's a waste.
> Besides, when createContainer, RocksDB.open cost about 200ms.
> So I will try to:
> 1. leader datanode and 2 follower datanodes create container in parallel, not
> in sequential.
> 2. optimize RocksDB.open.
> !screenshot-1.png!
--
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
