[ https://issues.apache.org/jira/browse/HDFS-10872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Krogen updated HDFS-10872: ------------------------------- Attachment: HDFS-10872-branch-2.012.patch Thank you for the commit, [~zhz]! I've attached a branch-2 patch. You were correct that the conflicts were just mechanical fixes - touching so many lines in {{FSNamesystem}} in a trivial way (just adding the operation name) caused many code conflicts but no real logical conflicts. > Add MutableRate metrics for FSNamesystemLock operations > ------------------------------------------------------- > > Key: HDFS-10872 > URL: https://issues.apache.org/jira/browse/HDFS-10872 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: namenode > Reporter: Erik Krogen > Assignee: Erik Krogen > Attachments: FSLockPerf.java, HDFS-10872-branch-2.012.patch, > HDFS-10872.000.patch, HDFS-10872.001.patch, HDFS-10872.002.patch, > HDFS-10872.003.patch, HDFS-10872.004.patch, HDFS-10872.005.patch, > HDFS-10872.006.patch, HDFS-10872.007.patch, HDFS-10872.008.patch, > HDFS-10872.009.patch, HDFS-10872.010.patch, HDFS-10872.011.patch, > HDFS-10872.012.patch, jmx-output > > > Add metrics for FSNamesystemLock operations to see, overall, how long each > operation is holding the lock for. Use MutableRate metrics for now. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org