[ https://issues.apache.org/jira/browse/HDFS-9145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026030#comment-15026030 ]
Jing Zhao commented on HDFS-9145: --------------------------------- Actually the value of {{writeLockInterval}} should be captured within the lock. The current code has a race on {{writeLockHeldTimeStamp}}. [~liuml07], do you want to fix this in a separate jira? > 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)