[
https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202391#comment-15202391
]
Bikas Saha commented on YARN-1040:
----------------------------------
This design doc effectively looks like a re-design of almost all core semantics
of YARN. This probably deserves a wider discussion on the dev email list and
under its own jira. Although it covers YARN-1040 and YARN-4726 the scope looks
much wider and careful thinking about backwards compatibility is needed etc.
Conceptually this changes the current semantic understanding of allocation and
container thats widely understood externally. I am afraid that this jira or
just the folks on this thread are not enough to make a decision for the given
proposal.
As far as this jira is concerned, both the previous (say a) & new (say b)
proposals sound similar with startContainer_in_a renamed to
startAllocation_in_b & startProcess_in_a renamed to startContainer_in_b. So we
may be fine in that restricted part minus the renamings.
> De-link container life cycle from an Allocation
> -----------------------------------------------
>
> Key: YARN-1040
> URL: https://issues.apache.org/jira/browse/YARN-1040
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Attachments: YARN-1040-rough-design.pdf
>
>
> The AM should be able to exec >1 process in a container, rather than have the
> NM automatically release the container when the single process exits.
> This would let an AM restart a process on the same container repeatedly,
> which for HBase would offer locality on a restarted region server.
> We may also want the ability to exec multiple processes in parallel, so that
> something could be run in the container while a long-lived process was
> already running. This can be useful in monitoring and reconfiguring the
> long-lived process, as well as shutting it down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
