Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 A7C5B75D5 for ; Fri, 14 Oct 2011 23:26:35 +0000 (UTC) Received: (qmail 57831 invoked by uid 500); 14 Oct 2011 23:26:35 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 57806 invoked by uid 500); 14 Oct 2011 23:26:35 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 57798 invoked by uid 99); 14 Oct 2011 23:26:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 23:26:35 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 23:26:33 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 105FF30807D for ; Fri, 14 Oct 2011 23:26:12 +0000 (UTC) Date: Fri, 14 Oct 2011 23:26:12 +0000 (UTC) From: "Hudson (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <40924775.16172.1318634772069.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <971021693.50278.1316607797609.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3057) Job History Server goes of OutOfMemory with 1200 Jobs and Heap Size set to 10 GB MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127980#comment-13127980 ] Hudson commented on MAPREDUCE-3057: ----------------------------------- Integrated in Hadoop-Mapreduce-trunk-Commit #1105 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1105/]) MAPREDUCE-3057. Job History Server goes of OutOfMemory with 1200 Jobs and Heap Size set to 10 GB. (Eric Payne via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1183545 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistory.java > Job History Server goes of OutOfMemory with 1200 Jobs and Heap Size set to 10 GB > -------------------------------------------------------------------------------- > > Key: MAPREDUCE-3057 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3057 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver, mrv2 > Affects Versions: 0.23.0 > Reporter: Karam Singh > Assignee: Eric Payne > Priority: Blocker > Fix For: 0.23.0 > > Attachments: MAPREDUCE-3057.v1.txt > > > History server was started with -Xmx10000m > Ran GridMix V3 with 1200 Jobs trace in STRESS mode on 350 nodes with each node 4 NMS. > All jobs finished as reported by RM Web UI and HADOOP_MAPRED_HOME/bin/mapred job -list all > But found that GridMix job client was stuck while trying connect to HistoryServer > Then tried to do HADOOP_MAPRED_HOME/bin/mapred job -status jobid > JobClient also got stuck while looking for token to connect to History server > Then looked at History Server logs and found History is trowing "java.lang.OutOfMemoryError: GC overhead limit exceeded" error. > With 10GB of Heap space and 1200 Jobs, History Server should not go out of memory . > No matter what are the type of jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira