hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11648) set DomainSocketWatcher thread name explicitly
Date Mon, 02 Mar 2015 09:32:05 GMT

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

Hadoop QA commented on HADOOP-11648:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12701794/HADOOP-11648-002.txt
  against trunk revision 30e73eb.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-common-project/hadoop-common
hadoop-hdfs-project/hadoop-hdfs.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5806//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5806//console

This message is automatically generated.

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

Mime
View raw message