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

Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/05/14 08:15:47 UTC

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

     [ https://issues.apache.org/jira/browse/HDFS-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HDFS-1573:
------------------------------

    Attachment: hdfs-1573.txt

Added some unit tests for LeaseRenewer, and fixed up the thread name.

> 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
>              Labels: newbie
>             Fix For: 0.23.0
>
>         Attachments: hdfs-1573.txt
>
>
> 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