hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1069) Deterministic MiniYARNCluster
Date Fri, 16 Aug 2013 19:12:47 GMT

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

Vinod Kumar Vavilapalli commented on YARN-1069:

At that point, aren't you better off trying to using MockRM, MockNM etc? Even though they
are named Mock*, they are the real ResourceManager, NodeManager except they don't start the
RPC servers.
> Deterministic MiniYARNCluster
> -----------------------------
>                 Key: YARN-1069
>                 URL: https://issues.apache.org/jira/browse/YARN-1069
>             Project: Hadoop YARN
>          Issue Type: Test
>    Affects Versions: 2.1.0-beta
>            Reporter: Maysam Yabandeh
>            Assignee: Maysam Yabandeh
>            Priority: Minor
> Currently the order of events in MiniYarnCluster is nondeterministic as the events are
triggered by scheduled timers. This makes it difficult to write tests since some erroneous
scenarios are triggered only after some particular sequence of events. An example is the bug
in YARN-779 where without this control over events, writing a deterministic unit test is not
possible. We should modify the source to allow both manual invocation of events as well as
via existing periodic timers. MiniYarnCluster can then expose such methods for more control
over events ordering.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message