[
https://issues.apache.org/jira/browse/HADOOP-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329516#comment-14329516
]
Colin Patrick McCabe commented on HADOOP-11604:
-----------------------------------------------
Thanks, guys. I am +1 on [~cnauroth]'s patch 004. I think it is a good
improvement.
I agree that it does not fix the root cause, here, though. We still don't know
why the thread exited. However, this is a good step forward that will
hopefully allow us to get more information later if necessary, as Chris
commented.
> 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
> Components: net
> Affects Versions: 2.6.0
> Reporter: Liang Xie
> Assignee: Chris Nauroth
> Priority: Critical
> Attachments: HADOOP-11604-001.txt, HADOOP-11604-002.txt,
> HADOOP-11604.003.patch, HADOOP-11604.004.patch
>
>
> 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)
