[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-09 Thread Hudson (JIRA)

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

Hudson commented on YARN-2649:
--

SUCCESS: Integrated in Hadoop-Yarn-trunk #706 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/706/])
YARN-2649. Fixed TestAMRMRPCNodeUpdates test failure. Contributed by Ming Ma 
(jianhe: rev e16e25ab1beac89c8d8be4e9f2a7fbefe81d35f3)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockRM.java
* hadoop-yarn-project/CHANGES.txt


 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
Assignee: Ming Ma
 Fix For: 2.6.0

 Attachments: YARN-2649-2.patch, YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from SUBMITTED to SCHEDULED
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-09 Thread Hudson (JIRA)

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

Hudson commented on YARN-2649:
--

FAILURE: Integrated in Hadoop-Hdfs-trunk #1896 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1896/])
YARN-2649. Fixed TestAMRMRPCNodeUpdates test failure. Contributed by Ming Ma 
(jianhe: rev e16e25ab1beac89c8d8be4e9f2a7fbefe81d35f3)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockRM.java
* hadoop-yarn-project/CHANGES.txt


 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
Assignee: Ming Ma
 Fix For: 2.6.0

 Attachments: YARN-2649-2.patch, YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from SUBMITTED to SCHEDULED
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-09 Thread Hudson (JIRA)

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

Hudson commented on YARN-2649:
--

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1921 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1921/])
YARN-2649. Fixed TestAMRMRPCNodeUpdates test failure. Contributed by Ming Ma 
(jianhe: rev e16e25ab1beac89c8d8be4e9f2a7fbefe81d35f3)
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockRM.java


 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
Assignee: Ming Ma
 Fix For: 2.6.0

 Attachments: YARN-2649-2.patch, YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from SUBMITTED to SCHEDULED
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-08 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on YARN-2649:
-

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

{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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc 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 2.0.3) 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/5327//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5327//console

This message is automatically generated.

 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
 Attachments: YARN-2649-2.patch, YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl 

[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-08 Thread Jian He (JIRA)

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

Jian He commented on YARN-2649:
---

Thank you , Ming !
Committing this.

 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
 Attachments: YARN-2649-2.patch, YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from SUBMITTED to SCHEDULED
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-08 Thread Hudson (JIRA)

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

Hudson commented on YARN-2649:
--

FAILURE: Integrated in Hadoop-trunk-Commit #6213 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/6213/])
YARN-2649. Fixed TestAMRMRPCNodeUpdates test failure. Contributed by Ming Ma 
(jianhe: rev e16e25ab1beac89c8d8be4e9f2a7fbefe81d35f3)
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockRM.java


 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
Assignee: Ming Ma
 Fix For: 2.6.0

 Attachments: YARN-2649-2.patch, YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from SUBMITTED to SCHEDULED
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-06 Thread Jian He (JIRA)

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

Jian He commented on YARN-2649:
---

[~mingma], thanks for working on this !
bq. Another way to fix it is to change MockRM.submitApp to waitForState on 
RMAppAttempt. That might address other test cases that use MockRM.submitApp.
I recently saw some other similar test failure e.g. YARN-2483.  maybe this is 
what we should do.  could you also run all tests locally, in case we don't 
introduce regression failure? thx 

 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
 Attachments: YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from SUBMITTED to SCHEDULED
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-2649) Flaky test TestAMRMRPCNodeUpdates

2014-10-06 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on YARN-2649:
-

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

{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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc 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 2.0.3) 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/5288//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5288//console

This message is automatically generated.

 Flaky test TestAMRMRPCNodeUpdates
 -

 Key: YARN-2649
 URL: https://issues.apache.org/jira/browse/YARN-2649
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
 Attachments: YARN-2649.patch


 Sometimes the test fails with the following error:
 testAMRMUnusableNodes(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates)
   Time elapsed: 41.73 sec   FAILURE!
 junit.framework.AssertionFailedError: AppAttempt state is not correct 
 (timedout) expected:ALLOCATED but was:SCHEDULED
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:382)
   at 
 org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates.testAMRMUnusableNodes(TestAMRMRPCNodeUpdates.java:125)
 When this happens, SchedulerEventType.NODE_UPDATE was processed before 
 RMAppAttemptEvent.ATTEMPT_ADDED was processed. That is possible, given the 
 test only waits for RMAppState.ACCEPTED before having NM sending heartbeat. 
 This can be reproduced using custom AsyncDispatcher with CountDownLatch. Here 
 is the log when this happens.
 {noformat}
 App State is : ACCEPTED
 2014-10-05 21:25:07,305 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) - 
 appattempt_1412569506932_0001_01 State change from NEW to SUBMITTED
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeStatusEvent.EventType:
  STATUS_UPDATE
 2014-10-05 21:25:07,305 DEBUG [AsyncDispatcher event handler] 
 rmnode.RMNodeImpl (RMNodeImpl.java:handle(384)) - Processing 127.0.0.1:1234 
 of type STATUS_UPDATE
 AppAttempt : appattempt_1412569506932_0001_01 State is : SUBMITTED 
 Waiting for state : ALLOCATED
 2014-10-05 21:25:07,306 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.AppAttemptAddedSchedulerEvent.EventType:
  APP_ATTEMPT_ADDED
 2014-10-05 21:25:07,328 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.NodeUpdateSchedulerEvent.EventType:
  NODE_UPDATE
 2014-10-05 21:25:07,330 DEBUG [AsyncDispatcher event handler] 
 event.AsyncDispatcher (AsyncDispatcher.java:dispatch(164)) - Dispatching the 
 event 
 org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEvent.EventType:
  ATTEMPT_ADDED
 2014-10-05 21:25:07,331 DEBUG [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(658)) - Processing 
 event for appattempt_1412569506932_0001_000
 001 of type ATTEMPT_ADDED
 2014-10-05 21:25:07,333 INFO  [AsyncDispatcher event handler] 
 attempt.RMAppAttemptImpl (RMAppAttemptImpl.java:handle(670)) -