[ https://issues.apache.org/jira/browse/HDFS-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993105#comment-12993105 ]
Todd Lipcon commented on HDFS-1573: ----------------------------------- I don't think so. I had a patch around somewhere, I'll see if I can find it and upload it (apparently forgot to when I made the JIRA) > LeaseChecker thread name trace not that useful > ---------------------------------------------- > > Key: HDFS-1573 > URL: https://issues.apache.org/jira/browse/HDFS-1573 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs client > Affects Versions: 0.23.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Priority: Trivial > Fix For: 0.23.0 > > > The LeaseChecker thread in DFSClient will put a stack trace in its thread > name, theoretically to help debug cases where these threads get leaked. > However it just shows the stack trace of whoever is asking for the thread's > name, not the stack trace of when the thread was allocated. I'd like to fix > this so that you can see where the thread got started, which was presumably > its original intent. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira