You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Kai Sasaki (JIRA)" <ji...@apache.org> on 2017/05/28 02:47:04 UTC

[jira] [Commented] (YARN-5927) BaseContainerManagerTest::waitForNMContainerState timeout accounting is not accurate

    [ https://issues.apache.org/jira/browse/YARN-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027677#comment-16027677 ] 

Kai Sasaki commented on YARN-5927:
----------------------------------

[~kasha@cloudera.com] I updated accordingly. Could you take a look when you have time?

> 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
>         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.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org