[
https://issues.apache.org/jira/browse/YARN-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691063#comment-15691063
]
Varun Saxena commented on YARN-5903:
------------------------------------
bq. Yes, we have seen consistent failures on some of our machines. My guess is
the thread that starts the resource manager is always delayed on that platform.
It is delayed so much so that client cannot reach the sever even with 10
retries.
Okay...The fix makes sense. Let me have a closer look.
> Fix race condition in TestResourceManagerAdministrationProtocolPBClientImpl
> beforeclass setup method
> ----------------------------------------------------------------------------------------------------
>
> Key: YARN-5903
> URL: https://issues.apache.org/jira/browse/YARN-5903
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Affects Versions: 3.0.0-alpha1
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Attachments: yarn5903.001.patch
>
>
> This is essentially the same race condition as in YARN-5901, that is,
> resourcemanager.getServiceState() == STATE.STARTED does not guarantee
> resource manager is fully started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
