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

Posted to common-issues@hadoop.apache.org by "Liang Xie (JIRA)" <ji...@apache.org> on 2015/03/02 06:46:05 UTC

[jira] [Commented] (HADOOP-11648) set DomainSocketWatcher thread name explicitly

    [ https://issues.apache.org/jira/browse/HADOOP-11648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342791#comment-14342791 ] 

Liang Xie commented on HADOOP-11648:
------------------------------------

How about v2, [~ozawa]

> 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
>         Attachments: HADOOP-11648-001.txt, HADOOP-11648-002.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)