[
https://issues.apache.org/jira/browse/HDFS-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035033#comment-13035033
]
Hudson commented on HDFS-1573:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #662 (See
[https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/662/])
HDFS-1573. Add useful tracing information to Lease Renewer thread names.
Contributed by Todd Lipcon.
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1104526
Files :
* /hadoop/hdfs/trunk/src/test/hdfs/org/apache/hadoop/hdfs/TestLeaseRenewer.java
* /hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/LeaseRenewer.java
* /hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/DFSClient.java
* /hadoop/hdfs/trunk/CHANGES.txt
> 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, hdfs-1573.txt, hdfs-1573.txt,
> 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
