[GitHub] [hadoop] brfrn169 edited a comment on issue #1954: HDFS-15217 Add more information to longest write/read lock held log

2020-04-18 Thread GitBox
brfrn169 edited a comment on issue #1954: HDFS-15217 Add more information to longest write/read lock held log URL: https://github.com/apache/hadoop/pull/1954#issuecomment-615893744 I did microbenchmarking with JMH. The microbenchmarking code is as follows: https://gist.github.com/brfrn1

[GitHub] [hadoop] brfrn169 edited a comment on issue #1954: HDFS-15217 Add more information to longest write/read lock held log

2020-04-15 Thread GitBox
brfrn169 edited a comment on issue #1954: HDFS-15217 Add more information to longest write/read lock held log URL: https://github.com/apache/hadoop/pull/1954#issuecomment-614352034 @goiri Okay. Will do that. This is an automa

[GitHub] [hadoop] brfrn169 edited a comment on issue #1954: HDFS-15217 Add more information to longest write/read lock held log

2020-04-15 Thread GitBox
brfrn169 edited a comment on issue #1954: HDFS-15217 Add more information to longest write/read lock held log URL: https://github.com/apache/hadoop/pull/1954#issuecomment-614281809 @goiri I don't think the overhead is very large because building the lock report message happens only when th