date:20130226


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

Hadoop QA commented on YARN-427:


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

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 tests included appear to have a timeout.{color}

{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-common.

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

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

This message is automatically generated.

 Coverage fix for org.apache.hadoop.yarn.server.api.*
 

 Key: YARN-427
 URL: https://issues.apache.org/jira/browse/YARN-427
 Project: Hadoop YARN
  Issue Type: Test
Affects Versions: 3.0.0, 0.23.7, 2.0.4-beta
Reporter: Aleksey Gorshkov
 Attachments: YARN-427-branch-2.patch, YARN-427-trunk.patch


 Coverage fix for org.apache.hadoop.yarn.server.api.*
 patch YARN-427-trunk.patch for trunk
 patch YARN-427-branch-2.patch for branch-2 and branch-0.23

--
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-365) Each NM heartbeat should not generate an event for the Scheduler


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

Hudson commented on YARN-365:
-

Integrated in Hadoop-Yarn-trunk #139 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/139/])
YARN-365. Change NM heartbeat handling to not generate a scheduler event on 
each heartbeat. (Contributed by Xuan Gong) (Revision 1450007)

 Result = SUCCESS
sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1450007
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNode.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNodeImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/UpdatedContainerInfo.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/event/NodeUpdateSchedulerEvent.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestFifoScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java


 Each NM heartbeat should not generate an event for the Scheduler
 

 Key: YARN-365
 URL: https://issues.apache.org/jira/browse/YARN-365
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager, scheduler
Affects Versions: 0.23.5
Reporter: Siddharth Seth
Assignee: Xuan Gong
 Fix For: 2.0.4-beta

 Attachments: Prototype2.txt, Prototype3.txt, YARN-365.10.patch, 
 YARN-365.1.patch, YARN-365.2.patch, YARN-365.3.patch, YARN-365.4.patch, 
 YARN-365.5.patch, YARN-365.6.patch, YARN-365.7.patch, YARN-365.8.patch, 
 YARN-365.9.patch


 Follow up from YARN-275
 https://issues.apache.org/jira/secure/attachment/12567075/Prototype.txt

--
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-390) ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, which causes test failures on Windows


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

Hudson commented on YARN-390:
-

Integrated in Hadoop-Yarn-trunk #139 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/139/])
YARN-390. ApplicationCLI and NodeCLI hard-coded platform-specific line 
separator causes test failures on Windows. Contributed by Chris Nauroth. 
(Revision 1449980)

 Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1449980
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ApplicationCLI.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/NodeCLI.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestYarnCLI.java


 ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, 
 which causes test failures on Windows
 -

 Key: YARN-390
 URL: https://issues.apache.org/jira/browse/YARN-390
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 3.0.0
Reporter: Chris Nauroth
Assignee: Chris Nauroth
 Attachments: YARN-390.1.patch, YARN-390.2.patch


 {{ApplicationCLI}}, {{NodeCLI}}, and the corresponding test {{TestYarnCLI}} 
 all use a hard-coded '\n' as the line separator.  This causes test failures 
 on Windows.

--
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-390) ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, which causes test failures on Windows


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

Hudson commented on YARN-390:
-

Integrated in Hadoop-Hdfs-trunk #1328 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1328/])
YARN-390. ApplicationCLI and NodeCLI hard-coded platform-specific line 
separator causes test failures on Windows. Contributed by Chris Nauroth. 
(Revision 1449980)

 Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1449980
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ApplicationCLI.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/NodeCLI.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestYarnCLI.java


 ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, 
 which causes test failures on Windows
 -

 Key: YARN-390
 URL: https://issues.apache.org/jira/browse/YARN-390
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 3.0.0
Reporter: Chris Nauroth
Assignee: Chris Nauroth
 Attachments: YARN-390.1.patch, YARN-390.2.patch


 {{ApplicationCLI}}, {{NodeCLI}}, and the corresponding test {{TestYarnCLI}} 
 all use a hard-coded '\n' as the line separator.  This causes test failures 
 on Windows.

--
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-365) Each NM heartbeat should not generate an event for the Scheduler


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

Hudson commented on YARN-365:
-

Integrated in Hadoop-Hdfs-trunk #1328 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1328/])
YARN-365. Change NM heartbeat handling to not generate a scheduler event on 
each heartbeat. (Contributed by Xuan Gong) (Revision 1450007)

 Result = FAILURE
sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1450007
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNode.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNodeImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/UpdatedContainerInfo.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/event/NodeUpdateSchedulerEvent.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestFifoScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java


 Each NM heartbeat should not generate an event for the Scheduler
 

 Key: YARN-365
 URL: https://issues.apache.org/jira/browse/YARN-365
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager, scheduler
Affects Versions: 0.23.5
Reporter: Siddharth Seth
Assignee: Xuan Gong
 Fix For: 2.0.4-beta

 Attachments: Prototype2.txt, Prototype3.txt, YARN-365.10.patch, 
 YARN-365.1.patch, YARN-365.2.patch, YARN-365.3.patch, YARN-365.4.patch, 
 YARN-365.5.patch, YARN-365.6.patch, YARN-365.7.patch, YARN-365.8.patch, 
 YARN-365.9.patch


 Follow up from YARN-275
 https://issues.apache.org/jira/secure/attachment/12567075/Prototype.txt

--
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-390) ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, which causes test failures on Windows


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

Hudson commented on YARN-390:
-

Integrated in Hadoop-Mapreduce-trunk #1356 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1356/])
YARN-390. ApplicationCLI and NodeCLI hard-coded platform-specific line 
separator causes test failures on Windows. Contributed by Chris Nauroth. 
(Revision 1449980)

 Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1449980
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ApplicationCLI.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/NodeCLI.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestYarnCLI.java


 ApplicationCLI and NodeCLI use hard-coded platform-specific line separator, 
 which causes test failures on Windows
 -

 Key: YARN-390
 URL: https://issues.apache.org/jira/browse/YARN-390
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 3.0.0
Reporter: Chris Nauroth
Assignee: Chris Nauroth
 Attachments: YARN-390.1.patch, YARN-390.2.patch


 {{ApplicationCLI}}, {{NodeCLI}}, and the corresponding test {{TestYarnCLI}} 
 all use a hard-coded '\n' as the line separator.  This causes test failures 
 on Windows.

--
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-365) Each NM heartbeat should not generate an event for the Scheduler


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

Hudson commented on YARN-365:
-

Integrated in Hadoop-Mapreduce-trunk #1356 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1356/])
YARN-365. Change NM heartbeat handling to not generate a scheduler event on 
each heartbeat. (Contributed by Xuan Gong) (Revision 1450007)

 Result = SUCCESS
sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1450007
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNode.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNodeImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/UpdatedContainerInfo.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/event/NodeUpdateSchedulerEvent.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestFifoScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java


 Each NM heartbeat should not generate an event for the Scheduler
 

 Key: YARN-365
 URL: https://issues.apache.org/jira/browse/YARN-365
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager, scheduler
Affects Versions: 0.23.5
Reporter: Siddharth Seth
Assignee: Xuan Gong
 Fix For: 2.0.4-beta

 Attachments: Prototype2.txt, Prototype3.txt, YARN-365.10.patch, 
 YARN-365.1.patch, YARN-365.2.patch, YARN-365.3.patch, YARN-365.4.patch, 
 YARN-365.5.patch, YARN-365.6.patch, YARN-365.7.patch, YARN-365.8.patch, 
 YARN-365.9.patch


 Follow up from YARN-275
 https://issues.apache.org/jira/secure/attachment/12567075/Prototype.txt

--
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-398) Allow white-list and black-list of resources


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

Arun C Murthy commented on YARN-398:


Alejandro - not clear what you mean by option #1 in YARN-392. I don't see any 
concrete proposal on YARN-392 such as http://s.apache.org/kV which provides an 
in-depth solution.

That discussion has veered off into groupIds, delay scheduling and hints - all 
of which seem unnecessary to accomplish the task at hand.

If I've missed it and it looks exactly like http://s.apache.org/kV then we all 
agree and can use YARN-392 and YARN-398 to work on FS  CS respectively. Makes 
sense?

 Allow white-list and black-list of resources
 

 Key: YARN-398
 URL: https://issues.apache.org/jira/browse/YARN-398
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Arun C Murthy
Assignee: Arun C Murthy

 Allow white-list and black-list of resources in scheduler api.

--
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] [Resolved] (YARN-424) Allow resource requests to provide hints to the scheduler


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

Arun C Murthy resolved YARN-424.


Resolution: Invalid

Looks like we agree Bikas. I'm going to resolve this as won't fix.

Please open specific jiras for specific features in the scheduler.

 Allow resource requests to provide hints to the scheduler 
 --

 Key: YARN-424
 URL: https://issues.apache.org/jira/browse/YARN-424
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: api, applications, scheduler
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza

 As initially discussed on YARN-392, it would be helpful for the allocate 
 protocol to be able to include hints to the scheduler.  Examples hints could 
 include deadlines (containers needed by a certain time) or gangs (resources 
 that should be scheduled at the same time or not at all).
 To avoid placing complex scheduling expectations on the RM, the restrictions 
 on hints would be:
 * Any scheduler may ignore any subset of hints. That is, applications must be 
 written to handle resource requests as if their hints don't exist.
 * Must be bounded in length - perhaps no larger than 16 bytes or 100 
 characters.

--
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] [Resolved] (YARN-428) YARNClientImpl logging too aggressively

2013-02-26 Thread Jason Lowe (JIRA)


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

Jason Lowe resolved YARN-428.
-

Resolution: Duplicate

 YARNClientImpl logging too aggressively
 ---

 Key: YARN-428
 URL: https://issues.apache.org/jira/browse/YARN-428
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.0.3-alpha
Reporter: Karthik Kambatla
Assignee: Karthik Kambatla
Priority: Trivial

 Every time we execute bin/hadoop job etc, the following two lines show up: 
 {noformat}
 13/02/26 07:05:19 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is inited.
 13/02/26 07:05:20 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is started.
 {noformat}

--
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-379) yarn [node,application] command print logger info messages

2013-02-26 Thread Karthik Kambatla (JIRA)


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

Karthik Kambatla commented on YARN-379:
---

Hi Abhishek, It might be better to change these INFO level messages to DEBUG.

 yarn [node,application] command print logger info messages
 --

 Key: YARN-379
 URL: https://issues.apache.org/jira/browse/YARN-379
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: Abhishek Kapoor
  Labels: usability
 Fix For: trunk-win

 Attachments: YARN-379.patch


 Running the yarn node and yarn applications command results in annoying log 
 info messages being printed:
 $ yarn node -list
 13/02/06 02:36:50 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is inited.
 13/02/06 02:36:50 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is started.
 Total Nodes:1
  Node-IdNode-State  Node-Http-Address   
 Health-Status(isNodeHealthy)Running-Containers
 foo:8041RUNNING  foo:8042   true  
  0
 13/02/06 02:36:50 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is stopped.
 $ yarn application
 13/02/06 02:38:47 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is inited.
 13/02/06 02:38:47 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is started.
 Invalid Command Usage : 
 usage: application
  -kill arg Kills the application.
  -list   Lists all the Applications from RM.
  -status arg   Prints the status of the application.
 13/02/06 02:38:47 INFO service.AbstractService: 
 Service:org.apache.hadoop.yarn.client.YarnClientImpl is stopped.

--
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-417) Add a poller that allows the AM to receive notifications when it is assigned containers

2013-02-26 Thread Chris Riccomini (JIRA)


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

Chris Riccomini commented on YARN-417:
--

Hey Sandy,

I think skipping onInit and onShutdown is fine. That stuff can be handled in 
the method that's actually instantiating/running the heartbeater.

So, to be concise: onReboot, onContainerLost (-100 return code), 
onContainerFailed (return code != 0 and != -100), onContainerSuccess (0 return 
code), onContainerAllocated. One other callback that is worth considering is 
onContainerOutOfMemory (-1 return code). I'm not sure how fine grained we want 
to get, but all these nuanced return codes that are hidden in the Java docs and 
whatnot make it difficult to write AMs. Doing as much work as possible for the 
framework developer would be a nice thing, in my opinion.

One thing that we need to be careful about is how a user would request 
containers using this callback approach and the AMRM. This line, from the 
Javadocs, scares me, App should not make concurrent allocate requests. May 
cause request loss. I think this means that AMRMClient.allocate can only be 
called in the heartbeat loop, and the user should use 
AMRMClient.addContainerRequest and AMRMClient.releaseAssignedContainer in the 
callbacks whenever it wants to get or release new containers. Bikas, is this a 
correct reading?

Cheers,
Chris

 Add a poller that allows the AM to receive notifications when it is assigned 
 containers
 ---

 Key: YARN-417
 URL: https://issues.apache.org/jira/browse/YARN-417
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: api, applications
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Attachments: YARN-417.patch, YarnAppMaster.java, 
 YarnAppMasterListener.java


 Writing AMs would be easier for some if they did not have to handle 
 heartbeating to the RM on their own.

--
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-417) Add a poller that allows the AM to receive notifications when it is assigned containers

2013-02-26 Thread Chris Riccomini (JIRA)

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

Chris Riccomini commented on YARN-417:
--

My first comment would be to see if we can provide this functionality via a
single object instead of a combination of AMRMClient, Heartbeater and
AllocationListener. Every new object and its combination with others
increases mental complexity.

Yeah, this was my initial inclination as well. I wanted some way to eliminate
the AMRMClient (applicationMasterHelper, in my case) by having the callbacks
return objects that signaled what they wanted. I couldn't come up with a scheme
that was simpler than just using the AMRMClient, though. If you guys can come
up with something that works, and is clean, I'm all ears.

Also, while callbacks are a reasonable approach, it would be good to spend a
little time thinking about other notification mechanisms like events or
futures.

Hmm, this is an interesting thought. Generally, I find futures easier to work
with, but as Sandy pointed out, I'm not sure how well it fits this model, where
you get updates that trickle in. It almost seems like a CountDownLatch for a
resource request could be used, but that seems more complex to deal with than a
callback. To riff on Sandy's API example, I could imagine something like:

{code}
ListContainer myAllocatedContainers =
heartbeater.submitContainerRequests().getContainers(3);
{code}

To wait for three containers before proceeding. You could also have
getContainers(), which would wait for all. This is very CountDownLatch-ish. I'm
not entirely sure how you might model the onReboot and failure/complete
scenarios, though. Thoughts? My imagination is failing me.

Something else to think about. completedContainers and allocatedContainers
are essentially coming at the same time. Breaking them into 2 calls may open
up ordering issues.

I had the same inclination that Sandy did, which was that I can see the need
for onComplete* before onAllocated, so that I can properly re-assign work to
allocated containers if an existing container failed, but beyond that, I
couldn't come up with a reason why you might want onAllocated before
onComplete*. I guess the question isn't so much about ordering, it's really: is
there ever a case where you need to know both what was allocated AND what was
completed at the same time, or in total (i.e. not one at a time)? I can't think
of anything.

Add a poller that allows the AM to receive notifications when it is assigned
containers
---

Key: YARN-417
URL: https://issues.apache.org/jira/browse/YARN-417
Project: Hadoop YARN
Issue Type: Sub-task
Components: api, applications
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
Attachments: YARN-417.patch, YarnAppMaster.java,
YarnAppMasterListener.java

Writing AMs would be easier for some if they did not have to handle
heartbeating to the RM on their own.

--
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-380) yarn node -status prints Last-Last-Node-Status

2013-02-26 Thread Thomas Graves (JIRA)


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

Thomas Graves commented on YARN-380:


Yeah I meant instead of Last-Last-Health-Update it should just be 
Last-Health-Update and in human readable date format. I'll fix the title.

 yarn node -status prints Last-Last-Node-Status
 --

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: Abhishek Kapoor
  Labels: usability

 I assume the Last-Last-NodeStatus is a typo and it should just be 
 Last-Node-Status.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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] [Updated] (YARN-380) yarn node -status prints Last-Last-Health-Update

2013-02-26 Thread Thomas Graves (JIRA)


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

Thomas Graves updated YARN-380:
---

Summary: yarn node -status prints Last-Last-Health-Update  (was: yarn node 
-status prints Last-Last-Node-Status)

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: Abhishek Kapoor
  Labels: usability

 I assume the Last-Last-NodeStatus is a typo and it should just be 
 Last-Node-Status.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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] [Updated] (YARN-380) yarn node -status prints Last-Last-Health-Update

2013-02-26 Thread Thomas Graves (JIRA)


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

Thomas Graves updated YARN-380:
---

Description: 
I assume the Last-Last-Health-Update is a typo and it should just be 
Last-Health-Update.


$ yarn node -status foo.com:8041
Node Report : 
Node-Id : foo.com:8041
Rack : /10.10.10.0
Node-State : RUNNING
Node-Http-Address : foo.com:8042
Health-Status(isNodeHealthy) : true
Last-Last-Health-Update : 1360118400219
Health-Report : 
Containers : 0
Memory-Used : 0M
Memory-Capacity : 24576

  was:
I assume the Last-Last-NodeStatus is a typo and it should just be 
Last-Node-Status.


$ yarn node -status foo.com:8041
Node Report : 
Node-Id : foo.com:8041
Rack : /10.10.10.0
Node-State : RUNNING
Node-Http-Address : foo.com:8042
Health-Status(isNodeHealthy) : true
Last-Last-Health-Update : 1360118400219
Health-Report : 
Containers : 0
Memory-Used : 0M
Memory-Capacity : 24576


 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: Abhishek Kapoor
  Labels: usability

 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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-417) Add a poller that allows the AM to receive notifications when it is assigned containers

2013-02-26 Thread Bikas Saha (JIRA)

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

Bikas Saha commented on YARN-417:
-

Yes. add/release should be used instead of allocate because allocate makes an
RPC that is subject to failures and race conditions. Its all handled in
AMRMClient.

While I like onContainer*() we need to think about proliferation of such
methods. A huge method listing tends to make me cautious because I have to
understand all those methods. Also, I have a gut feeling that there might be a
lot of user code replication for each callback. I like it when code is in one
place. How about an onContainerGoodName() and then provide a helper method
that tells whether the container is completed, successfull, killed,
outofmemory. IMO, this might be more flexible and less verbose. And the user
handling logic is in one place.

One other thought, is that where possible, the callbacks should return
collection/list of objects. Say, we have a large job and we are getting 100's
of containers. For perf, it might be better to not have 100's of calls for
onContainerAllocated() and onContainerCompleted().

Now that we have 2 example codes and some discussion, lets post a concrete
interface declaration with javadoc. That will help focus the discussion and we
can converge quickly.

Add a poller that allows the AM to receive notifications when it is assigned
containers
---

Writing AMs would be easier for some if they did not have to handle
heartbeating to the RM on their own.

[jira] [Commented] (YARN-398) Allow white-list and black-list of resources

2013-02-26 Thread Alejandro Abdelnur (JIRA)


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

Alejandro Abdelnur commented on YARN-398:
-

Option #1 in YARN-392 is 
https://issues.apache.org/jira/browse/YARN-392?focusedCommentId=13576322page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13576322



 Allow white-list and black-list of resources
 

 Key: YARN-398
 URL: https://issues.apache.org/jira/browse/YARN-398
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Arun C Murthy
Assignee: Arun C Murthy

 Allow white-list and black-list of resources in scheduler api.

--
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-417) Add a poller that allows the AM to receive notifications when it is assigned containers

2013-02-26 Thread Karthik Kambatla (JIRA)


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

Karthik Kambatla commented on YARN-417:
---

How about following Netty kind of asynchrony? YARNContainerFuture for waiting 
purposes, and onContainerComplete(ContainerStatus) for asynchronous 
notification?

 Add a poller that allows the AM to receive notifications when it is assigned 
 containers
 ---

 Key: YARN-417
 URL: https://issues.apache.org/jira/browse/YARN-417
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: api, applications
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Attachments: YARN-417.patch, YarnAppMaster.java, 
 YarnAppMasterListener.java


 Writing AMs would be easier for some if they did not have to handle 
 heartbeating to the RM on their own.

--
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-398) Allow white-list and black-list of resources


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

Arun C Murthy commented on YARN-398:


There are no details there. Furthermore it says:

bq.  An issue with this is that it would be impossible to make a request like 
I want a container to be only on one of these two nodes.

The proposal I have does support that very use-case since it continues to exist 
the current scheduling mechanism... so, I'm not sure how the two are related. 


 Allow white-list and black-list of resources
 

 Key: YARN-398
 URL: https://issues.apache.org/jira/browse/YARN-398
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Arun C Murthy
Assignee: Arun C Murthy

 Allow white-list and black-list of resources in scheduler api.

--
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] [Created] (YARN-429) capacity-scheduler config missing from yarn-test artifact

2013-02-26 Thread Siddharth Seth (JIRA)

Siddharth Seth created YARN-429:
---

 Summary: capacity-scheduler config missing from yarn-test artifact
 Key: YARN-429
 URL: https://issues.apache.org/jira/browse/YARN-429
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.0.3-alpha
Reporter: Siddharth Seth
Assignee: Siddharth Seth
Priority: Blocker


MiniYARNCluster and MiniMRCluster are unusable by downstream projects with the 
2.0.3-alpha release, since the capacity-scheduler configuration is missing from 
the test artifact.
hadoop-yarn-server-tests-3.0.0-SNAPSHOT-tests.jar should include the default 
capacity-scheduler configuration. Also, this doesn't need to be part of the 
default classpath - and should be moved out of the top level directory in the 
dist package.

--
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] [Assigned] (YARN-380) yarn node -status prints Last-Last-Health-Update


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

omkar vinit joshi reassigned YARN-380:
--

Assignee: omkar vinit joshi  (was: Abhishek Kapoor)

Abhishek, I already have a patch for this, I am taking this over.

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability

 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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] [Updated] (YARN-380) yarn node -status prints Last-Last-Health-Update


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

omkar vinit joshi updated YARN-380:
---

Attachment: yarn-380.patch

It has fixed the Last-Last-Health-Update issue and is also formatting the 
date. -MM-dd'T'HH:mm:ssZZ format is used for date. 

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: yarn-380.patch


 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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-380) yarn node -status prints Last-Last-Health-Update


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

Hadoop QA commented on YARN-380:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12571041/yarn-380.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/435//console

This message is automatically generated.

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: yarn-380.patch


 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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] [Updated] (YARN-429) capacity-scheduler config missing from yarn-test artifact

2013-02-26 Thread Siddharth Seth (JIRA)


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

Siddharth Seth updated YARN-429:


Attachment: YARN-429.txt

Patch to include capacity-scheduler.xml in 
hadoop-yarn-server-tests-${version}-tests.jar

Also changes the dist packaging to move this file under 
'share/hadoop/yarn/test' instead of 'share/hadoop/yarn'.

Is there a standard location for test-jars - instead of share/hadoop/yarn/test ?

 capacity-scheduler config missing from yarn-test artifact
 -

 Key: YARN-429
 URL: https://issues.apache.org/jira/browse/YARN-429
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.0.3-alpha
Reporter: Siddharth Seth
Assignee: Siddharth Seth
Priority: Blocker
 Attachments: YARN-429.txt


 MiniYARNCluster and MiniMRCluster are unusable by downstream projects with 
 the 2.0.3-alpha release, since the capacity-scheduler configuration is 
 missing from the test artifact.
 hadoop-yarn-server-tests-3.0.0-SNAPSHOT-tests.jar should include the default 
 capacity-scheduler configuration. Also, this doesn't need to be part of the 
 default classpath - and should be moved out of the top level directory in the 
 dist package.

--
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-429) capacity-scheduler config missing from yarn-test artifact


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

Arun C Murthy commented on YARN-429:


This might have been caused by YARN-140, investigating further.

 capacity-scheduler config missing from yarn-test artifact
 -

 Key: YARN-429
 URL: https://issues.apache.org/jira/browse/YARN-429
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.0.3-alpha
Reporter: Siddharth Seth
Assignee: Siddharth Seth
Priority: Blocker
 Attachments: YARN-429.txt


 MiniYARNCluster and MiniMRCluster are unusable by downstream projects with 
 the 2.0.3-alpha release, since the capacity-scheduler configuration is 
 missing from the test artifact.
 hadoop-yarn-server-tests-3.0.0-SNAPSHOT-tests.jar should include the default 
 capacity-scheduler configuration. Also, this doesn't need to be part of the 
 default classpath - and should be moved out of the top level directory in the 
 dist package.

--
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-398) Allow white-list and black-list of resources


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

Arun C Murthy commented on YARN-398:


IAC, as I've said before: if it's the same proposal... then great, we all 
agree. Let's get it done.

 Allow white-list and black-list of resources
 

 Key: YARN-398
 URL: https://issues.apache.org/jira/browse/YARN-398
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Arun C Murthy
Assignee: Arun C Murthy

 Allow white-list and black-list of resources in scheduler api.

--
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] [Updated] (YARN-426) Failure to download a public resource on a node prevents further downloads of the resource from that node

2013-02-26 Thread Jason Lowe (JIRA)


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

Jason Lowe updated YARN-426:


Attachment: YARN-426.patch

Patch to ensure all queued attempts for a public resource are notified of a 
failed localization and the attempts are dequeued.

 Failure to download a public resource on a node prevents further downloads of 
 the resource from that node
 -

 Key: YARN-426
 URL: https://issues.apache.org/jira/browse/YARN-426
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.0.3-alpha, 0.23.6
Reporter: Jason Lowe
Assignee: Jason Lowe
Priority: Critical
 Attachments: YARN-426.patch


 If the NM encounters an error while downloading a public resource, it fails 
 to empty the list of request events corresponding to the resource request in 
 {{attempts}}.  If the same public resource is subsequently requested on that 
 node, {{PublicLocalizer.addResource}} will skip the download since it will 
 mistakenly believe a download of that resource is already in progress.  At 
 that point any container that requests the public resource will just hang in 
 the {{LOCALIZING}} state.

--
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] [Updated] (YARN-380) yarn node -status prints Last-Last-Health-Update


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

omkar vinit joshi updated YARN-380:
---

Attachment: issue-yarn-380.patch

Updating the patch.

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: issue-yarn-380.patch


 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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] [Updated] (YARN-380) yarn node -status prints Last-Last-Health-Update


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

omkar vinit joshi updated YARN-380:
---

Attachment: (was: yarn-380.patch)

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: issue-yarn-380.patch


 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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-410) Miscellaneous web UI issues

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

omkar vinit joshi commented on YARN-410:

below 2 issues
1) Remove the Note column from the application list. When a failure happens,
this Note spoils the table layout.
and
2) The per-application page has all the RM related information like version,
start-time etc. Must be some accidental change by one of the patches.

are no longer present.

Miscellaneous web UI issues
---

Key: YARN-410
URL: https://issues.apache.org/jira/browse/YARN-410
Project: Hadoop YARN
Issue Type: Bug
Reporter: Vinod Kumar Vavilapalli
Labels: usability

We need to fix the following issues on YARN web-UI:
- Remove the Note column from the application list. When a failure
happens, this Note spoils the table layout.
- When the Application is still not running, the Tracking UI should be title
UNASSIGNED, for some reason it is titled ApplicationMaster but
(correctly) links to #.
- The per-application page has all the RM related information like version,
start-time etc. Must be some accidental change by one of the patches.
- The diagnostics for a failed app on the per-application page don't retain
new lines and wrap'em around - looks hard to read.

[jira] [Assigned] (YARN-410) Miscellaneous web UI issues


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

omkar vinit joshi reassigned YARN-410:
--

Assignee: omkar vinit joshi

 Miscellaneous web UI issues
 ---

 Key: YARN-410
 URL: https://issues.apache.org/jira/browse/YARN-410
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Vinod Kumar Vavilapalli
Assignee: omkar vinit joshi
  Labels: usability

 We need to fix the following issues on YARN web-UI:
  - Remove the Note column from the application list. When a failure 
 happens, this Note spoils the table layout.
  - When the Application is still not running, the Tracking UI should be title 
 UNASSIGNED, for some reason it is titled ApplicationMaster but 
 (correctly) links to #.
  - The per-application page has all the RM related information like version, 
 start-time etc. Must be some accidental change by one of the patches.
  - The diagnostics for a failed app on the per-application page don't retain 
 new lines and wrap'em around - looks hard to read.

--
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] [Updated] (YARN-410) Miscellaneous web UI issues

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

omkar vinit joshi updated YARN-410:
---

Attachment: yarn-410.patch

Fixing the last issues
The diagnostics for a failed app on the per-application page don't retain new
lines and wrap'em around - looks hard to read

When multiline diagnostic information is received then it will add div tags
for every line as '\n' doesn't work inside td.

Miscellaneous web UI issues
---

Key: YARN-410
URL: https://issues.apache.org/jira/browse/YARN-410
Project: Hadoop YARN
Issue Type: Bug
Reporter: Vinod Kumar Vavilapalli
Assignee: omkar vinit joshi
Labels: usability
Attachments: yarn-410.patch

[jira] [Commented] (YARN-380) yarn node -status prints Last-Last-Health-Update


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

Hadoop QA commented on YARN-380:


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

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 tests included appear to have a timeout.{color}

{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:red}-1 eclipse:eclipse{color}.  The patch failed to build 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-client.

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

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

This message is automatically generated.

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: issue-yarn-380.patch


 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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-426) Failure to download a public resource on a node prevents further downloads of the resource from that node


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

Hadoop QA commented on YARN-426:


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

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 tests included appear to have a timeout.{color}

{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-nodemanager.

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

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

This message is automatically generated.

 Failure to download a public resource on a node prevents further downloads of 
 the resource from that node
 -

 Key: YARN-426
 URL: https://issues.apache.org/jira/browse/YARN-426
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.0.3-alpha, 0.23.6
Reporter: Jason Lowe
Assignee: Jason Lowe
Priority: Critical
 Attachments: YARN-426.patch


 If the NM encounters an error while downloading a public resource, it fails 
 to empty the list of request events corresponding to the resource request in 
 {{attempts}}.  If the same public resource is subsequently requested on that 
 node, {{PublicLocalizer.addResource}} will skip the download since it will 
 mistakenly believe a download of that resource is already in progress.  At 
 that point any container that requests the public resource will just hang in 
 the {{LOCALIZING}} state.

--
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-410) Miscellaneous web UI issues


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

Hadoop QA commented on YARN-410:


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

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

  {color:red}-1 one of tests included doesn't have a timeout.{color}

{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-common.

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

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

This message is automatically generated.

 Miscellaneous web UI issues
 ---

 Key: YARN-410
 URL: https://issues.apache.org/jira/browse/YARN-410
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Vinod Kumar Vavilapalli
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: yarn-410.patch


 We need to fix the following issues on YARN web-UI:
  - Remove the Note column from the application list. When a failure 
 happens, this Note spoils the table layout.
  - When the Application is still not running, the Tracking UI should be title 
 UNASSIGNED, for some reason it is titled ApplicationMaster but 
 (correctly) links to #.
  - The per-application page has all the RM related information like version, 
 start-time etc. Must be some accidental change by one of the patches.
  - The diagnostics for a failed app on the per-application page don't retain 
 new lines and wrap'em around - looks hard to read.

--
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] [Updated] (YARN-410) Miscellaneous web UI issues


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

omkar vinit joshi updated YARN-410:
---

Attachment: yarn-410.patch

adding timeout parameter in Test.

 Miscellaneous web UI issues
 ---

 Key: YARN-410
 URL: https://issues.apache.org/jira/browse/YARN-410
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Vinod Kumar Vavilapalli
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: yarn-410.patch


 We need to fix the following issues on YARN web-UI:
  - Remove the Note column from the application list. When a failure 
 happens, this Note spoils the table layout.
  - When the Application is still not running, the Tracking UI should be title 
 UNASSIGNED, for some reason it is titled ApplicationMaster but 
 (correctly) links to #.
  - The per-application page has all the RM related information like version, 
 start-time etc. Must be some accidental change by one of the patches.
  - The diagnostics for a failed app on the per-application page don't retain 
 new lines and wrap'em around - looks hard to read.

--
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] [Updated] (YARN-410) Miscellaneous web UI issues


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

omkar vinit joshi updated YARN-410:
---

Attachment: (was: yarn-410.patch)

 Miscellaneous web UI issues
 ---

 Key: YARN-410
 URL: https://issues.apache.org/jira/browse/YARN-410
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Vinod Kumar Vavilapalli
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: yarn-410.patch


 We need to fix the following issues on YARN web-UI:
  - Remove the Note column from the application list. When a failure 
 happens, this Note spoils the table layout.
  - When the Application is still not running, the Tracking UI should be title 
 UNASSIGNED, for some reason it is titled ApplicationMaster but 
 (correctly) links to #.
  - The per-application page has all the RM related information like version, 
 start-time etc. Must be some accidental change by one of the patches.
  - The diagnostics for a failed app on the per-application page don't retain 
 new lines and wrap'em around - looks hard to read.

--
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-380) yarn node -status prints Last-Last-Health-Update


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

omkar vinit joshi commented on YARN-380:


mvn eclipse:eclipse works locally with patch. Trying to submit the patch 
again.

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: issue-yarn-380.patch


 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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] [Updated] (YARN-380) yarn node -status prints Last-Last-Health-Update


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

omkar vinit joshi updated YARN-380:
---

Attachment: (was: issue-yarn-380.patch)

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability

 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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] [Updated] (YARN-380) yarn node -status prints Last-Last-Health-Update


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

omkar vinit joshi updated YARN-380:
---

Attachment: issue-yarn-380.patch

 yarn node -status prints Last-Last-Health-Update
 

 Key: YARN-380
 URL: https://issues.apache.org/jira/browse/YARN-380
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.0.3-alpha
Reporter: Thomas Graves
Assignee: omkar vinit joshi
  Labels: usability
 Attachments: issue-yarn-380.patch


 I assume the Last-Last-Health-Update is a typo and it should just be 
 Last-Health-Update.
 $ yarn node -status foo.com:8041
 Node Report : 
 Node-Id : foo.com:8041
 Rack : /10.10.10.0
 Node-State : RUNNING
 Node-Http-Address : foo.com:8042
 Health-Status(isNodeHealthy) : true
 Last-Last-Health-Update : 1360118400219
 Health-Report : 
 Containers : 0
 Memory-Used : 0M
 Memory-Capacity : 24576

--
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-410) Miscellaneous web UI issues