Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E6CDEDD10 for ; Thu, 25 Oct 2012 12:41:18 +0000 (UTC) Received: (qmail 97093 invoked by uid 500); 25 Oct 2012 12:41:18 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 96638 invoked by uid 500); 25 Oct 2012 12:41:16 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 96365 invoked by uid 99); 25 Oct 2012 12:41:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2012 12:41:15 +0000 Date: Thu, 25 Oct 2012 12:41:15 +0000 (UTC) From: "Hudson (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1960027442.27111.1351168875133.JavaMail.jiratomcat@arcas> In-Reply-To: <139267965.65329.1350588603501.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HADOOP-8942) Thundering herd of RPCs with large responses leads to OOM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484077#comment-13484077 ] Hudson commented on HADOOP-8942: -------------------------------- Integrated in Hadoop-Hdfs-0.23-Build #415 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/415/]) MAPREDUCE-4730. Fix Reducer's EventFetcher to scale the map-completion requests slowly to avoid HADOOP-8942. Contributed by Jason Lowe. svn merge --ignore-ancestry -c 1401941 ../../trunk/ (Revision 1401943) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1401943 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/EventFetcher.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/Shuffle.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/task/reduce/TestEventFetcher.java > Thundering herd of RPCs with large responses leads to OOM > --------------------------------------------------------- > > Key: HADOOP-8942 > URL: https://issues.apache.org/jira/browse/HADOOP-8942 > Project: Hadoop Common > Issue Type: Bug > Components: ipc > Affects Versions: 0.23.3 > Reporter: Jason Lowe > > When a large number of clients are all making calls with large amounts of response data then the IPC server can exhaust memory. See MAPREDUCE-4730 for an example of this. > There does not appear to be any flow control between the server's handler threads and the responder thread. If a handler thread cannot write out all of the response data without blocking, it queues up the remainder for the responder thread and goes back to the next call in the call queue. If there are enough clients, this can cause the handler threads to overwhelm the heap by queueing response data faster than it can be processed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira