[ https://issues.apache.org/jira/browse/HDFS-15808?focusedWorklogId=556117&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-556117 ]
ASF GitHub Bot logged work on HDFS-15808: ----------------------------------------- Author: ASF GitHub Bot Created on: 23/Feb/21 01:23 Start Date: 23/Feb/21 01:23 Worklog Time Spent: 10m Work Description: tomscut removed a comment on pull request #2668: URL: https://github.com/apache/hadoop/pull/2668#issuecomment-780595016 > This message was automatically generated. Hi @anuengineer, the failed check looks unrelated to the change. May I ask how I should deal with it? ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 556117) Time Spent: 5h 20m (was: 5h 10m) > 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 20m > Remaining Estimate: 0h > > To monitor how often read/write locks exceed thresholds, we can add two > metrics(ReadLockWarning/WriteLockWarning), which are exposed in JMX. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org