[
https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013013#comment-14013013
]
Sandy Ryza commented on YARN-1368:
----------------------------------
Regardless of the technical approach taken in any initial patch, my
understanding of basic JIRA practice is that assigning a JIRA to oneself (as
Anubhav did here) means "give me some space to work on this". Because Hadoop
development is so distributed, it acts as a good coordination mechanism that
helps us all avoid duplicating work. Of course, we don't want people to be
able to sit on JIRAs and stall progress, but a simple "Will you be able to get
to this soon? If not, mind if I take it up?" and then waiting a couple of days
usually suffices to deal with that.
Etiquette is obviously difficult to codify, and I realize that this discussion
is detracting from the technical details of this JIRA, so I'll stop my
belly-aching here.
> 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.2.patch, YARN-1368.3.patch,
> YARN-1368.4.patch, YARN-1368.5.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
(v6.2#6252)
