Return-Path: 
 <mapreduce-issues-return-39361-apmail-hadoop-mapreduce-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 3328F9E32
	for <apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org>;
 Tue, 31 Jan 2012 04:04:49 +0000 (UTC)
Received: (qmail 44288 invoked by uid 500); 31 Jan 2012 04:04:48 -0000
Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org
Received: (qmail 43960 invoked by uid 500); 31 Jan 2012 04:04:37 -0000
Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-issues@hadoop.apache.org>
List-Id: <mapreduce-issues.hadoop.apache.org>
Reply-To: mapreduce-issues@hadoop.apache.org
Delivered-To: mailing list mapreduce-issues@hadoop.apache.org
Received: (qmail 43913 invoked by uid 99); 31 Jan 2012 04:04:34 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2012 04:04:34 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_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; Tue, 31 Jan 2012 04:04:31 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 5F440180B96
	for <mapreduce-issues@hadoop.apache.org>;
 Tue, 31 Jan 2012 04:04:10 +0000 (UTC)
Date: Tue, 31 Jan 2012 04:04:10 +0000 (UTC)
From: "Ramya Sunil (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1733597700.10462.1327982650391.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1383174443.2996.1327712231955.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3748) Move CS related nodeUpdate log
 messages to DEBUG
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-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramya Sunil updated MAPREDUCE-3748:
-----------------------------------

    Attachment: MAPREDUCE-3748.patch

Resubmitting the patch.
                
> Move CS related nodeUpdate log messages to DEBUG
> ------------------------------------------------
>
>                 Key: MAPREDUCE-3748
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3748
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Ramya Sunil
>            Assignee: Ramya Sunil
>            Priority: Minor
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3748.patch, MAPREDUCE-3748.patch
>
>
> Currently, the RM has nodeUpdate logs per NM per second such as the following:
> 2012-01-27 21:51:32,429 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: nodeUpdate: <nodemanager1>:<port1> clusterResources: memory: 57344
> 2012-01-27 21:51:32,510 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: nodeUpdate: <nodemanager2>:<port2> clusterResources: memory: 57344
> 2012-01-27 21:51:33,094 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: nodeUpdate: <nodemanager1>:<port1> clusterResources: memory: 57344
> Debugging is difficult with huge amount of logs such as this. These logs need to be moved to DEBUG.

--
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