You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ramya Sunil (Created) (JIRA)" <ji...@apache.org> on 2012/01/28 01:57:11 UTC
[jira] [Created] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
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
Priority: Minor
Fix For: 0.23.1
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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196664#comment-13196664 ]
Hadoop QA commented on MAPREDUCE-3748:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12512507/MAPREDUCE-3748.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 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+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 .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1719//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1719//console
This message is automatically generated.
> 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
>
>
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196708#comment-13196708 ]
Hadoop QA commented on MAPREDUCE-3748:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12512529/MAPREDUCE-3748.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 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+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 .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1720//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1720//console
This message is automatically generated.
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196878#comment-13196878 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #155 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/155/])
Merge -c 1238157 from trunk to branch-0.23 to fix MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238159
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196744#comment-13196744 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Common-0.23-Commit #450 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/450/])
Merge -c 1238157 from trunk to branch-0.23 to fix MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238159
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196741#comment-13196741 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #1693 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1693/])
MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug. Contributed by Ramya Sunil.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238157
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Mahadev konar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196632#comment-13196632 ]
Mahadev konar commented on MAPREDUCE-3748:
------------------------------------------
@Ramya,
Can you reupload the patch and also grant license to Apache?
> 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
>
>
> 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
[jira] [Updated] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Arun C Murthy (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196866#comment-13196866 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #942 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/942/])
MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug. Contributed by Ramya Sunil.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238157
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Updated] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Ramya Sunil (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramya Sunil updated MAPREDUCE-3748:
-----------------------------------
Status: Patch Available (was: Open)
> 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
>
>
> 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
[jira] [Assigned] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Ramya Sunil (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramya Sunil reassigned MAPREDUCE-3748:
--------------------------------------
Assignee: Ramya Sunil
> 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
>
>
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196754#comment-13196754 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #1638 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1638/])
MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug. Contributed by Ramya Sunil.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238157
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196924#comment-13196924 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Build #177 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/177/])
Merge -c 1238157 from trunk to branch-0.23 to fix MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238159
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196755#comment-13196755 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #465 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/465/])
Merge -c 1238157 from trunk to branch-0.23 to fix MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238159
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196742#comment-13196742 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Commit #441 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/441/])
Merge -c 1238157 from trunk to branch-0.23 to fix MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238159
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Updated] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Ramya Sunil (Updated) (JIRA)" <ji...@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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196738#comment-13196738 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #1621 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1621/])
MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug. Contributed by Ramya Sunil.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238157
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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
[jira] [Updated] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Ramya Sunil (Updated) (JIRA)" <ji...@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
A simple one liner fix.
> 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
>
>
> 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
[jira] [Commented] (MAPREDUCE-3748) Move CS related nodeUpdate log
messages to DEBUG
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196931#comment-13196931 ]
Hudson commented on MAPREDUCE-3748:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #975 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/975/])
MAPREDUCE-3748. Changed a log in CapacityScheduler.nodeUpdate to debug. Contributed by Ramya Sunil.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238157
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> 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