[ https://issues.apache.org/jira/browse/HDFS-10682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412249#comment-15412249 ]
Chen Liang edited comment on HDFS-10682 at 8/8/16 6:44 PM: ----------------------------------------------------------- The failed tests are unrelated and seem to be tests that fail frequently recently, see: HADOOP-13469 which tracks TestRefreshUserMappings fail HDFS-10732 which tracks TestTracing fail was (Author: vagarychen): The failed tests are unrelated and seem to be failing frequently recently, see: HADOOP-13469 which tracks TestRefreshUserMappings fail HDFS-10732 which tracks TestTracing fail > 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 > Attachments: 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org