hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen Liang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10682) Replace FsDatasetImpl object lock with a separate lock object
Date Mon, 29 Aug 2016 17:35:20 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446514#comment-15446514

Chen Liang commented on HDFS-10682:

I am also thinking of a better way of doing this. Will definitely look at you JIRA, thanks!

> 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: 2.8.0
>         Attachments: HDFS-10682-branch-2.001.patch, HDFS-10682-branch-2.002.patch, HDFS-10682-branch-2.003.patch,
HDFS-10682-branch-2.004.patch, HDFS-10682-branch-2.005.patch, HDFS-10682-branch-2.006.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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message