You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/01/10 21:26:46 UTC

[jira] Created: (HDFS-1573) LeaseChecker thread name trace not that useful

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.
-
You can reply to this email to add a comment to the issue online.