[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13497014#comment-13497014
]
Hudson commented on MAPREDUCE-4517:
---
Integrated in Hadoop-Yarn-trunk #36 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/36/])
MAPREDUCE-4517. Too many INFO messages written out during AM to RM
heartbeat (Jason Lowe via tgraves) (Revision 1409032)
Result = SUCCESS
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13497058#comment-13497058
]
Hudson commented on MAPREDUCE-4517:
---
Integrated in Hadoop-Hdfs-0.23-Build #435 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/435/])
merge -r 1409031:1409032 from trunk. FIXES: MAPREDUCE-4517 (Revision
1409035)
Result = SUCCESS
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1409035
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13497066#comment-13497066
]
Hudson commented on MAPREDUCE-4517:
---
Integrated in Hadoop-Hdfs-trunk #1226 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1226/])
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-SVNview=revrev=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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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-SVNview=revrev=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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496292#comment-13496292
]
Thomas Graves commented on MAPREDUCE-4517:
--
Mostly looks good. How about we take one more of the updateAndLogIfChanged
calls out though and only call it once before Scheduling and then once after
the assign (outside of the if block) and then in getResource add a log message
for the # new or finished containers. This way we cut the logging down but I
think still get the crucial information. I think assign and getResource
already have other log messages that will allow us to build up what happens in
between.
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
Attachments: 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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496522#comment-13496522
]
Hadoop QA commented on MAPREDUCE-4517:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553363/MAPREDUCE-4517.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3027//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3027//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
Affects Versions: 0.23.1, 2.0.1-alpha
Reporter: James Kinley
Assignee: Jason Lowe
Priority: Minor
Labels: patch
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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496677#comment-13496677
]
Thomas Graves commented on MAPREDUCE-4517:
--
+1 looks good. Thanks Jason!
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
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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496686#comment-13496686
]
Hudson commented on MAPREDUCE-4517:
---
Integrated in Hadoop-trunk-Commit #3011 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3011/])
MAPREDUCE-4517. Too many INFO messages written out during AM to RM
heartbeat (Jason Lowe via tgraves) (Revision 1409032)
Result = SUCCESS
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13495953#comment-13495953
]
Hadoop QA commented on MAPREDUCE-4517:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553265/MAPREDUCE-4517.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3020//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3020//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3020//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
Affects Versions: 0.23.1, 2.0.1-alpha
Reporter: James Kinley
Assignee: Jason Lowe
Priority: Minor
Labels: patch
Attachments: 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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13495984#comment-13495984
]
Hadoop QA commented on MAPREDUCE-4517:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553271/MAPREDUCE-4517.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 13 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3021//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3021//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3021//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
Affects Versions: 0.23.1, 2.0.1-alpha
Reporter: James Kinley
Assignee: Jason Lowe
Priority: Minor
Labels: patch
Attachments: 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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496020#comment-13496020
]
Hadoop QA commented on MAPREDUCE-4517:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553278/MAPREDUCE-4517.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3022//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3022//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
Affects Versions: 0.23.1, 2.0.1-alpha
Reporter: James Kinley
Assignee: Jason Lowe
Priority: Minor
Labels: patch
Attachments: 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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13452932#comment-13452932
]
James Kinley commented on MAPREDUCE-4517:
-
No new tests required. Only changed logging level from INFO to DEBUG.
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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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/1252/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());
ListContainer 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
[jira] [Commented] (MAPREDUCE-4517) Too many INFO messages written out during AM to RM heartbeat
[
https://issues.apache.org/jira/browse/MAPREDUCE-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13429185#comment-13429185
]
Hadoop QA commented on MAPREDUCE-4517:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12539306/MAPREDUCE-4517.patch
against trunk revision .
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2710//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());
ListContainer 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
