hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3748) Move CS related nodeUpdate log messages to DEBUG
Date Tue, 31 Jan 2012 06:25:10 GMT

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

Arun C Murthy updated MAPREDUCE-3748:
-------------------------------------

          Resolution: Fixed
    Target Version/s: 0.23.1
              Status: Resolved  (was: Patch Available)

I just committed this after a minor change to add a isDebugEnabled check. Thanks Ramya!
                
> 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

        

Mime
View raw message