hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3533) Test: Fix launchAM in MockRM to wait for attempt to be scheduled
Date Thu, 23 Apr 2015 05:11:39 GMT

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

sandflee commented on YARN-3533:

thanks for you patch,  
1, waitForSchedulerAppAttemptAdded may be not done as expected 
in waitForSchedulerAppAttemptAdded.
  public T getApplicationAttempt(ApplicationAttemptId applicationAttemptId) {
    SchedulerApplication<T> app =
    return app == null ? null : app.getCurrentAppAttempt();

as above shows, this func just get the current appAttempt not the appAttempt correspongding
to applicationAttemptId. (A BUG?)

2,  SCHEDULED is not a stable state,  is it possible other nm heartbeat makes it becomes allocated,
 wait for this state will be blocked?

> Test: Fix launchAM in MockRM to wait for attempt to be scheduled
> ----------------------------------------------------------------
>                 Key: YARN-3533
>                 URL: https://issues.apache.org/jira/browse/YARN-3533
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 2.6.0
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>         Attachments: YARN-3533.001.patch
> MockRM#launchAM fails in many test runs because it does not wait for the app attempt
to be scheduled before NM update is sent as noted in [recent builds|https://issues.apache.org/jira/browse/YARN-3387?focusedCommentId=14507255&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14507255]

This message was sent by Atlassian JIRA

View raw message