[ 
https://issues.apache.org/jira/browse/HDFS-15808?focusedWorklogId=559433&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559433
 ]

ASF GitHub Bot logged work on HDFS-15808:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Mar/21 15:58
            Start Date: 01/Mar/21 15:58
    Worklog Time Spent: 10m 
      Work Description: tomscut commented on pull request #2668:
URL: https://github.com/apache/hadoop/pull/2668#issuecomment-788061149


   Hi @arp7 , could you take a quick look at this? Let's see if there are any 
other questions. Thank you.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 559433)
    Time Spent: 5h 50m  (was: 5h 40m)

> Add metrics for FSNamesystem read/write lock hold long time
> -----------------------------------------------------------
>
>                 Key: HDFS-15808
>                 URL: https://issues.apache.org/jira/browse/HDFS-15808
>             Project: Hadoop HDFS
>          Issue Type: Wish
>          Components: hdfs
>            Reporter: tomscut
>            Assignee: tomscut
>            Priority: Major
>              Labels: hdfs, lock, metrics, pull-request-available
>         Attachments: ExpiredHeartbeat.png, lockLongHoldCount
>
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> To monitor how often read/write locks exceed thresholds, we can add two 
> metrics(ReadLockLongHoldCount/WriteLockLongHoldCount), which are exposed in 
> JMX.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to