[
https://issues.apache.org/jira/browse/HADOOP-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322696#comment-14322696
]
Hadoop QA commented on HADOOP-11604:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12699082/HADOOP-11604-001.txt
against trunk revision ab0b958.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5713//console
This message is automatically generated.
> Reach xceiver limit once the watcherThread die
> ----------------------------------------------
>
> Key: HADOOP-11604
> URL: https://issues.apache.org/jira/browse/HADOOP-11604
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Priority: Critical
> Attachments: HADOOP-11604-001.txt
>
>
> Our product cluster hit the Xceiver limit even w/ HADOOP-10404 &
> HADOOP-11333, i found it was caused by DomainSocketWatcher.watcherThread
> gone. Attached is a possible fix, please review, thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
