Apache
/
hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge r1490437 from trunk to branch-2 for YARN-761. TestNMClientAsync fails sometimes (Zhijie Shen via bikas) 

git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2@1490440 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Bikas Saha 2013-06-06 20:55:02 +00:00
parent bbafbced87
commit 99aff64f1a
2 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
hadoop-yarn-project/CHANGES.txt
View File

@ -278,6 +278,9 @@ Release 2.1.0-beta - UNRELEASED
YARN-756. Move Preemption* records to yarn.api where they really belong. YARN-756. Move Preemption* records to yarn.api where they really belong.
(Jian He via vinodkv) (Jian He via vinodkv)
YARN-750. Allow for black-listing resources in YARN API and Impl in CS
(acmurthy via bikas)
OPTIMIZATIONS OPTIMIZATIONS
YARN-512. Log aggregation root directory check is more expensive than it YARN-512. Log aggregation root directory check is more expensive than it
@ -449,6 +452,8 @@ Release 2.1.0-beta - UNRELEASED
YARN-764. blank Used Resources on Capacity Scheduler page (Nemon Lou via YARN-764. blank Used Resources on Capacity Scheduler page (Nemon Lou via
tgraves) tgraves)
YARN-761. TestNMClientAsync fails sometimes (Zhijie Shen via bikas)
BREAKDOWN OF HADOOP-8562 SUBTASKS AND RELATED JIRAS BREAKDOWN OF HADOOP-8562 SUBTASKS AND RELATED JIRAS
YARN-158. Yarn creating package-info.java must not depend on sh. YARN-158. Yarn creating package-info.java must not depend on sh.

7
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/TestNMClientAsync.java
View File

@ -121,8 +121,11 @@ public class TestNMClientAsync {
} }
Assert.assertEquals("Error occurs in ContainerEventProcessor", 0, Assert.assertEquals("Error occurs in ContainerEventProcessor", 0,
((MockNMClientAsync1) asyncClient).errorMsgs.size()); ((MockNMClientAsync1) asyncClient).errorMsgs.size());
Assert.assertEquals("Completed container is not removed", 0, // When the callback functions are all executed, the event processor threads
asyncClient.containers.size()); // may still not terminate and the containers may still not removed.
while (asyncClient.containers.size() > 0) {
Thread.sleep(10);
}
asyncClient.stop(); asyncClient.stop();
Assert.assertFalse( Assert.assertFalse(
"The thread of Container Management Event Dispatcher is still alive", "The thread of Container Management Event Dispatcher is still alive",