Toshihiro Suzuki created HDFS-15217: ---------------------------------------
Summary: Add more information to longest write/read lock held log Key: HDFS-15217 URL: https://issues.apache.org/jira/browse/HDFS-15217 Project: Hadoop HDFS Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Currently, we can see the stack trace in the longest write/read lock held log, but sometimes we need more information, for example, a target path of deletion: {code:java} 2020-03-10 21:51:21,116 [main] INFO namenode.FSNamesystem (FSNamesystemLock.java:writeUnlock(276)) - Number of suppressed write-lock reports: 0 Longest write-lock held at 2020-03-10 21:51:21,107+0900 for 6ms via java.lang.Thread.getStackTrace(Thread.java:1559) org.apache.hadoop.util.StringUtils.getStackTrace(StringUtils.java:1058) org.apache.hadoop.hdfs.server.namenode.FSNamesystemLock.writeUnlock(FSNamesystemLock.java:257) org.apache.hadoop.hdfs.server.namenode.FSNamesystemLock.writeUnlock(FSNamesystemLock.java:233) org.apache.hadoop.hdfs.server.namenode.FSNamesystem.writeUnlock(FSNamesystem.java:1706) org.apache.hadoop.hdfs.server.namenode.FSNamesystem.delete(FSNamesystem.java:3188) ... {code} Adding more information (opName, path, etc.) to the log is useful to troubleshoot. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org