Vinod Kumar Vavilapalli commented on YARN-1368:

Thanks for the udpate! This looks oh-so-close. Some more comments, including 
review of tests now:
 - YarnConfiguration.RM_WORK_PRESERVING_RECOVERY_ENABLED as Private?
 - Also say that in yarn-default.xml that the feature is experimental now.
 - o.a.h.y.s.rm.Applicatoin changes seem unnecessary?
 - MockAM.allocateContainers() is added but not used.
 - MockRM why reduce the sleeps?
 - TestMoveApplication changes are unnecessary?
 - There is a bunch of "settle down" sleeps. May be in future tickets, we 
should fix them.

> Common work to re-populate containers’ state into scheduler
> -----------------------------------------------------------
>                 Key: YARN-1368
>                 URL: https://issues.apache.org/jira/browse/YARN-1368
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Jian He
>         Attachments: YARN-1368.1.patch, YARN-1368.10.patch, 
> YARN-1368.2.patch, YARN-1368.3.patch, YARN-1368.4.patch, YARN-1368.5.patch, 
> YARN-1368.7.patch, YARN-1368.8.patch, YARN-1368.9.patch, 
> YARN-1368.combined.001.patch, YARN-1368.preliminary.patch
> YARN-1367 adds support for the NM to tell the RM about all currently running 
> containers upon registration. The RM needs to send this information to the 
> schedulers along with the NODE_ADDED_EVENT so that the schedulers can recover 
> the current allocation state of the cluster.

This message was sent by Atlassian JIRA

Reply via email to