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 "Yufei Gu (JIRA)" <ji...@apache.org> on 2016/04/07 08:23:25 UTC
[jira] [Updated] (YARN-4907) Make all MockRM#waitForState
consistent.
[ https://issues.apache.org/jira/browse/YARN-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yufei Gu updated YARN-4907:
---------------------------
Description:
There are some inconsistencies among these {{waitForState}} in {{MockRM}}:
1. Some return a boolean, some don't.
2. Some wait function don't have a timeout, they can wait for ever.
3. Some use {{LOG.info}} and others use {{System.out.println}} to print messages.
was:
There are some inconsistencies among these {{waitForState}} in {{MockRM}}:
1. Some return a boolean, some don't.
2. Some have a minimum waiting time(1000ms), some one don't. I appreciate if someone can explain why we need a minimum waiting time.
3. Some wait function don't have a timeout, they can wait for ever.
4. Some use LOG.info and others use {{System.out.println}} to print messages.
> Make all MockRM#waitForState consistent.
> -----------------------------------------
>
> Key: YARN-4907
> URL: https://issues.apache.org/jira/browse/YARN-4907
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Yufei Gu
> Assignee: Yufei Gu
>
> There are some inconsistencies among these {{waitForState}} in {{MockRM}}:
> 1. Some return a boolean, some don't.
> 2. Some wait function don't have a timeout, they can wait for ever.
> 3. Some use {{LOG.info}} and others use {{System.out.println}} to print messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)