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] [Updated] (HADOOP-11604) Reach xceiver limit once the watcherThread die
Date Tue, 17 Feb 2015 14:17:12 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Liang Xie updated HADOOP-11604:
-------------------------------
    Attachment: HADOOP-11604-002.txt

Thanks for review, uploaded a new patch to address comment.
xceiver reached the upper limit because no thread to signal processedCond after the watcherThread
die. then all xceiver threads hung always at processedCond.await

> 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, HADOOP-11604-002.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)

Mime
View raw message