hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liang Xie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11648) set DomainSocketWatcher thread name explicitly
Date Tue, 03 Mar 2015 03:34:04 GMT

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

Liang Xie commented on HADOOP-11648:

seems the Hadoop QA didn't work?    the new patch doesn't have any "@author" info...

> 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, 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

View raw message