[ https://issues.apache.org/jira/browse/HDFS-9145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955784#comment-14955784 ]
Hudson commented on HDFS-9145: ------------------------------ FAILURE: Integrated in Hadoop-Yarn-trunk #1259 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1259/]) HDFS-9145. Tracking methods that hold FSNamesytemLock for too long. (wheat9: rev d1e1925bf6c3cf7fd23ed8df5a5e18677fc299d8) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSNamesystem.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java * hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/GenericTestUtils.java > Tracking methods that hold FSNamesytemLock for too long > ------------------------------------------------------- > > Key: HDFS-9145 > URL: https://issues.apache.org/jira/browse/HDFS-9145 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Reporter: Jing Zhao > Assignee: Mingliang Liu > Fix For: 2.8.0 > > Attachments: HDFS-9145.000.patch, HDFS-9145.001.patch, > HDFS-9145.002.patch, HDFS-9145.003.patch > > > It will be helpful that if we can have a way to track (or at least log a msg) > if some operation is holding the FSNamesystem lock for a long time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)