[
https://issues.apache.org/jira/browse/HDFS-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123392#comment-17123392
]
Xiaoqiao He commented on HDFS-15382:
------------------------------------
Thanks [~Aiphag0] for your proposal here. The performance improvement is
impressive especially the load of DataNode is very high. A few nits,
a. the monitor index is our internal item, it is more helpful to explain what
it is meaning.
b. it is confused with {{ReplicaCachingGetSpaceUsed}}, IIUC,
{{ReplicaCachingGetSpaceUsed}} is calculated in memory directly rather than
sync info from disk, right? so why is it related to this changes? Also the log
print is based on our internal version rather than branch trunk, some notes
could be better.
c. If could we offer a simple design document (maybe include one design chart
with a simple design/refactor description), IMO it is useful to someone who is
interested this improvement.
> Split FsDatasetImpl from blockpool lock to blockpool volume lock
> -----------------------------------------------------------------
>
> Key: HDFS-15382
> URL: https://issues.apache.org/jira/browse/HDFS-15382
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Aiphago
> Assignee: Aiphago
> Priority: Major
> Fix For: 3.2.1
>
> Attachments: image-2020-06-02-1.png
>
>
> In HDFS-15180 we split lock to blockpool grain size.But when one volume is in
> heavy load and will block other request which in same blockpool but different
> volume.So we split lock to two leval to avoid this happend.And to improve
> datanode performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
