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 562A5D4AA for ; Mon, 10 Sep 2012 09:09:14 +0000 (UTC) Received: (qmail 3444 invoked by uid 500); 10 Sep 2012 09:09:14 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 3041 invoked by uid 500); 10 Sep 2012 09:09:10 -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 2965 invoked by uid 99); 10 Sep 2012 09:09:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 09:09:08 +0000 Date: Mon, 10 Sep 2012 20:09:07 +1100 (NCT) From: "Hadoop QA (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1237542042.56894.1347268148021.JavaMail.jiratomcat@arcas> In-Reply-To: <567310599.15128.1344195722381.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat 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/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451831#comment-13451831 ] Hadoop QA commented on MAPREDUCE-4517: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12544442/MAPREDUCE-4517.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. 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. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2833//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2833//console This message is automatically generated. > Too many INFO messages written out during AM to RM heartbeat > ------------------------------------------------------------ > > Key: MAPREDUCE-4517 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4517 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: applicationmaster > Reporter: James Kinley > Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: MAPREDUCE-4517.patch > > > Too many INFO log messages written out during AM to RM heartbeat. Based on default frequency of 1000ms (scheduler.heartbeat.interval-ms) either 2 or 4 INFO messages are written out per second: > LOG.info("Before Scheduling: " + getStat()); > List allocatedContainers = getResources(); > LOG.info("After Scheduling: " + getStat()); > if (allocatedContainers.size() > 0) { > LOG.info("Before Assign: " + getStat()); > scheduledRequests.assign(allocatedContainers); > LOG.info("After Assign: " + getStat()); > } > These should probably be changed to DEBUG message to save the log growing too quickly. -- 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