[ https://issues.apache.org/jira/browse/HADOOP-11648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsuyoshi Ozawa updated HADOOP-11648: ------------------------------------ Resolution: Fixed Fix Version/s: 2.7.0 Status: Resolved (was: Patch Available) Committed this to trunk and branch-2. Thanks Liang for your contribution and thanks Colin Patrick McCabe for your review. > Set DomainSocketWatcher thread name explicitly > ---------------------------------------------- > > Key: HADOOP-11648 > URL: https://issues.apache.org/jira/browse/HADOOP-11648 > Project: Hadoop Common > Issue Type: Improvement > Components: net > Affects Versions: 2.6.0 > Reporter: Liang Xie > Assignee: Liang Xie > Fix For: 2.7.0 > > Attachments: HADOOP-11648-001.txt, HADOOP-11648-002.txt, > HADOOP-11648-003.txt > > > while working at HADOOP-11604, seems the current DomainSocketWatcher thread > name is not set explicitly, e.g. in our cluster, the format is like: > Thread-25, Thread-303670 or sth else. Here Thread-25 seems came from > Datanode.initDataXceiver, and once this thread die, the Xceiver leak will be > found. I think it'd better to set the thread name, so we can debug issue > easier in further. -- This message was sent by Atlassian JIRA (v6.3.4#6332)