[
https://issues.apache.org/jira/browse/HDFS-15180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450379#comment-17450379
]
Stephen O'Donnell commented on HDFS-15180:
------------------------------------------
In Cloudera, we have not been looking into this issue actively, but it is an
interesting one. We have went ahead with HDFS-15160 in our latest release and
so far have not seen any problems from it. Our hope is the relatively minor
change in HDFS-15160 can have a large benefit and is easy to disable with a
config switch if any problems are detected. This change probably has a bigger
impact that HDFS-15160, but is more complicated and so carries more risk.
It is good to know you have been running it with no issue for some time - that
does help give us more confidence there are no issues with the approach.
> DataNode FsDatasetImpl Fine-Grained Locking via BlockPool.
> -----------------------------------------------------------
>
> Key: HDFS-15180
> URL: https://issues.apache.org/jira/browse/HDFS-15180
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Affects Versions: 3.2.0
> Reporter: Qi Zhu
> Assignee: Aiphago
> Priority: Major
> Attachments: HDFS-15180.001.patch, HDFS-15180.002.patch,
> HDFS-15180.003.patch, HDFS-15180.004.patch,
> image-2020-03-10-17-22-57-391.png, image-2020-03-10-17-31-58-830.png,
> image-2020-03-10-17-34-26-368.png, image-2020-04-09-11-20-36-459.png
>
>
> Now the FsDatasetImpl datasetLock is heavy, when their are many namespaces in
> big cluster. If we can split the FsDatasetImpl datasetLock via blockpool.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
