[
https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987155#comment-13987155
]
Vinod Kumar Vavilapalli commented on YARN-1368:
-----------------------------------------------
bq. I think the prototype is doing as a scheduler-specifc fashion and only for
the FairScheduler. It'll be a maintenance overhead if we implement each
scheduler separately.
This makes sense. As much as possible, RM restart should be orthogonal to
schedulers. Further, where possible, we should try to reuse code within the
schedulers. That way we won't miss stuff like metrics, scheduler calculations,
resource consumption etc.
> 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: Anubhav Dhoot
> Attachments: 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
(v6.2#6252)
