hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yufei Gu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5901) Fix race condition in TestGetGroups beforeclass setup()
Date Mon, 21 Nov 2016 23:50:58 GMT

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

Yufei Gu commented on YARN-5901:

Thanks [~haibochen] for the patch. The patch looks great.
One nit: can we provide meaningful error messages if RM doesn't start in 60s?

> Fix race condition in TestGetGroups beforeclass setup()
> -------------------------------------------------------
>                 Key: YARN-5901
>                 URL: https://issues.apache.org/jira/browse/YARN-5901
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Haibo Chen
>            Assignee: Haibo Chen
>              Labels: unittest
>         Attachments: yarn5901.001.patch
> In TestGetGroups, the class-level setup method spins up, in a child thread, a resource
manager that Yarn clients can talk to. But it checks whether the resource manager is fully
started by doing resourcemanager.getServiceState() == STATE.STARTED. This is not reliable
since resourcemanager.start() will first trigger service state change in RM, and then starts
up all the services added to RM. We need to wait for RM to fully start before YARN clients
 can send requests. Otherwise, the tests can fail due to "connection refused"  exception when
the main thread sends out client requests to RM and if the RPC server has not fired up in
the child thread.  

This message was sent by Atlassian JIRA

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

View raw message