[jira] [Commented] (YARN-305) Too many 'Node offerred to app:... messages in RM

2013-10-11 Thread Sandy Ryza (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13793048#comment-13793048
 ] 

Sandy Ryza commented on YARN-305:
-

+1

 Too many 'Node offerred to app:... messages in RM
 --

 Key: YARN-305
 URL: https://issues.apache.org/jira/browse/YARN-305
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Reporter: Lohit Vijayarenu
Assignee: Lohit Vijayarenu
Priority: Critical
 Attachments: YARN-305.1.patch, YARN-305.2.patch


 Running fair scheduler YARN shows that RM has lots of messages like the below.
 {noformat}
 INFO 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable: 
 Node offered to app: application_1357147147433_0002 reserved: false
 {noformat}
 They dont seem to tell much and same line is dumped many times in RM log. It 
 would be good to have it improved with node information or moved to some 
 other logging level with enough debug information



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (YARN-305) Too many 'Node offerred to app:... messages in RM

2013-09-17 Thread Joep Rottinghuis (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770065#comment-13770065
 ] 

Joep Rottinghuis commented on YARN-305:
---

Marking as critical. W/o this patch the RM log is filled with superfluous 
messages, masking real issues.

 Too many 'Node offerred to app:... messages in RM
 --

 Key: YARN-305
 URL: https://issues.apache.org/jira/browse/YARN-305
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Reporter: Lohit Vijayarenu
Assignee: Lohit Vijayarenu
Priority: Critical
 Attachments: YARN-305.1.patch, YARN-305.2.patch


 Running fair scheduler YARN shows that RM has lots of messages like the below.
 {noformat}
 INFO 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable: 
 Node offered to app: application_1357147147433_0002 reserved: false
 {noformat}
 They dont seem to tell much and same line is dumped many times in RM log. It 
 would be good to have it improved with node information or moved to some 
 other logging level with enough debug information

--
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] (YARN-305) Too many 'Node offerred to app:... messages in RM

2013-09-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762241#comment-13762241
 ] 

Hadoop QA commented on YARN-305:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12602204/YARN-305.2.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:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1883//console

This message is automatically generated.

 Too many 'Node offerred to app:... messages in RM
 --

 Key: YARN-305
 URL: https://issues.apache.org/jira/browse/YARN-305
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Reporter: Lohit Vijayarenu
Assignee: Lohit Vijayarenu
Priority: Minor
 Attachments: YARN-305.1.patch, YARN-305.2.patch


 Running fair scheduler YARN shows that RM has lots of messages like the below.
 {noformat}
 INFO 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable: 
 Node offered to app: application_1357147147433_0002 reserved: false
 {noformat}
 They dont seem to tell much and same line is dumped many times in RM log. It 
 would be good to have it improved with node information or moved to some 
 other logging level with enough debug information

--
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] (YARN-305) Too many 'Node offerred to app:... messages in RM

2013-09-02 Thread Karthik Kambatla (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756225#comment-13756225
 ] 

Karthik Kambatla commented on YARN-305:
---

Can any of the committers add Lohit as a contributor on the project, so he can 
pick it up? 

 Too many 'Node offerred to app:... messages in RM
 --

 Key: YARN-305
 URL: https://issues.apache.org/jira/browse/YARN-305
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Reporter: Lohit Vijayarenu
Priority: Minor
 Attachments: YARN-305.1.patch


 Running fair scheduler YARN shows that RM has lots of messages like the below.
 {noformat}
 INFO 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable: 
 Node offered to app: application_1357147147433_0002 reserved: false
 {noformat}
 They dont seem to tell much and same line is dumped many times in RM log. It 
 would be good to have it improved with node information or moved to some 
 other logging level with enough debug information

--
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] (YARN-305) Too many 'Node offerred to app:... messages in RM

2013-08-14 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740201#comment-13740201
 ] 

Hadoop QA commented on YARN-305:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12598058/YARN-305.1.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1716//console

This message is automatically generated.

 Too many 'Node offerred to app:... messages in RM
 --

 Key: YARN-305
 URL: https://issues.apache.org/jira/browse/YARN-305
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Reporter: Lohit Vijayarenu
Priority: Minor
 Attachments: YARN-305.1.patch


 Running fair scheduler YARN shows that RM has lots of messages like the below.
 {noformat}
 INFO 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable: 
 Node offered to app: application_1357147147433_0002 reserved: false
 {noformat}
 They dont seem to tell much and same line is dumped many times in RM log. It 
 would be good to have it improved with node information or moved to some 
 other logging level with enough debug information

--
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] (YARN-305) Too many 'Node offerred to app:... messages in RM

2013-08-14 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740264#comment-13740264
 ] 

Hadoop QA commented on YARN-305:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12598064/YARN-305.1.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-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/1718//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1718//console

This message is automatically generated.

 Too many 'Node offerred to app:... messages in RM
 --

 Key: YARN-305
 URL: https://issues.apache.org/jira/browse/YARN-305
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Reporter: Lohit Vijayarenu
Priority: Minor
 Attachments: YARN-305.1.patch


 Running fair scheduler YARN shows that RM has lots of messages like the below.
 {noformat}
 INFO 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable: 
 Node offered to app: application_1357147147433_0002 reserved: false
 {noformat}
 They dont seem to tell much and same line is dumped many times in RM log. It 
 would be good to have it improved with node information or moved to some 
 other logging level with enough debug information

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