[
https://issues.apache.org/jira/browse/HDFS-10682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414957#comment-15414957
]
Jingcheng Du commented on HDFS-10682:
-------------------------------------
Thanks a lot [~fenghua_hu], and thanks [~arpitagarwal] for linking HDFS-9668.
According to Colin's suggestion, the changes would be minor.
I updated only a few methods in FsDatasetImpl and moved the disk operations out
of the synchronized block, and planned to post it soon after merging this JIRA
HDFS-10682.
> Replace FsDatasetImpl object lock with a separate lock object
> -------------------------------------------------------------
>
> Key: HDFS-10682
> URL: https://issues.apache.org/jira/browse/HDFS-10682
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: Chen Liang
> Assignee: Chen Liang
> Fix For: 3.0.0-alpha2
>
> Attachments: HDFS-10682-branch-2.001.patch,
> HDFS-10682-branch-2.002.patch, HDFS-10682-branch-2.003.patch,
> HDFS-10682.001.patch, HDFS-10682.002.patch, HDFS-10682.003.patch,
> HDFS-10682.004.patch, HDFS-10682.005.patch, HDFS-10682.006.patch,
> HDFS-10682.007.patch, HDFS-10682.008.patch, HDFS-10682.009.patch,
> HDFS-10682.010.patch
>
>
> This Jira proposes to replace the FsDatasetImpl object lock with a separate
> lock object. Doing so will make it easier to measure lock statistics like
> lock held time and warn about potential lock contention due to slow disk
> operations.
> Right now we can use org.apache.hadoop.util.AutoCloseableLock. In the future
> we can also consider replacing the lock with a read-write lock.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
