[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497086#comment-13497086
]
Hudson commented on MAPREDUCE-4517:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #1257 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1257/])
MAPREDUCE-4517. Too many INFO messages written out during AM to RM
heartbeat (Jason Lowe via tgraves) (Revision 1409032)
Result = FAILURE
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1409032
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java
> 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
> Affects Versions: 0.23.1, 2.0.1-alpha
> Reporter: James Kinley
> Assignee: Jason Lowe
> Priority: Minor
> Labels: patch
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: MAPREDUCE-4517.patch, MAPREDUCE-4517.patch,
> MAPREDUCE-4517.patch, MAPREDUCE-4517.patch, 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<Container> 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
