hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11648) Set DomainSocketWatcher thread name explicitly
Date Thu, 05 Mar 2015 14:52:41 GMT

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

Hudson commented on HADOOP-11648:
---------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #114 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/114/])
HADOOP-11648. Set DomainSocketWatcher thread name explicitly. Contributed by Liang Xie. (ozawa:
rev 74a4754d1c790b8740a4221f276aa571bc5dbfd5)
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/unix/TestDomainSocketWatcher.java
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/unix/DomainSocketWatcher.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/ShortCircuitRegistry.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/shortcircuit/DfsClientShmManager.java


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

Mime
View raw message