[
https://issues.apache.org/jira/browse/YARN-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123934#comment-16123934
]
Hudson commented on YARN-5927:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12168 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/12168/])
YARN-5927. BaseContainerManagerTest::waitForNMContainerState timeout (kasha:
rev 8c4b6d16a526610a03ccc85665744ad071e37400)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/BaseContainerManagerTest.java
> BaseContainerManagerTest::waitForNMContainerState timeout accounting is not
> accurate
> ------------------------------------------------------------------------------------
>
> Key: YARN-5927
> URL: https://issues.apache.org/jira/browse/YARN-5927
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Miklos Szegedi
> Assignee: Kai Sasaki
> Priority: Trivial
> Labels: newbie
> Fix For: 2.9.0, 3.0.0-beta1
>
> Attachments: YARN-5917.01.patch, YARN-5917.02.patch,
> YARN-5927.03.patch
>
>
> See below that timeoutSecs is increased twice. We also do a sleep right away
> before even checking the observed value.
> {code}
> do {
> Thread.sleep(2000);
> ...
> timeoutSecs += 2;
> } while (!finalStates.contains(currentState)
> && timeoutSecs++ < timeOutMax);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
