[
https://issues.apache.org/jira/browse/HDFS-9145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950894#comment-14950894
]
Jing Zhao commented on HDFS-9145:
---------------------------------
I think here we do not need to use a stack to track multi-entrance scenario,
considering 1) the current code usually do not grab the write lock multiple
times, and 2) the information about the total holding time of a thread may be
good enough for us. So we can only use the hold count information to track the
time between last_unlock and first_lock.
> 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
> Attachments: HDFS-9145.000.patch, HDFS-9145.001.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)
