Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-1573

LeaseChecker thread name trace not that useful

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 0.23.0
    • Fix Version/s: 0.23.0
    • Component/s: hdfs-client
    • Labels:
    • Hadoop Flags:
      Reviewed

      Description

      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.

      1. hdfs-1573.txt
        12 kB
        Todd Lipcon
      2. hdfs-1573.txt
        12 kB
        Todd Lipcon
      3. hdfs-1573.txt
        12 kB
        Todd Lipcon
      4. hdfs-1573.txt
        12 kB
        Todd Lipcon

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Todd Lipcon
            Reporter:
            Todd Lipcon
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development