[
https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208906#comment-15208906
]
Bikas Saha commented on YARN-1040:
----------------------------------
It would be great if existing apps can use the changes in YARN-1040 to be able
to run more than a single process (sequentially or concurrently). If we use
YARN-1040 to build the primitives here then those primitives could be used for
the broader work designed for services (which seems to be indicated in the
design doc). Without YARN-1040, existing java based apps cannot use features
like increasing container memory because the JVM has to be restarted before it
can grow to a larger size. I can see the argument of asking users to use new
APIs for new features but requiring existing apps to change their AM/RM
implementations (that have been stabilized with much effort) just to be able to
launch multiple processes does not seem empathetic.
Separately from this, I have not been actively involved in the project for a
while. Hence my understanding of the scope and semantic changes proposed in it
may be stale and I may be inaccurate in thinking that these are fundamental
enough to be done in a special jira for that purpose for a wider discussion.
You guys can make a call on that.
> 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)
