hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2518) Support in-process container executor
Date Sat, 13 Dec 2014 19:53:14 GMT

    [ https://issues.apache.org/jira/browse/YARN-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245508#comment-14245508

Vinod Kumar Vavilapalli commented on YARN-2518:

bq. Yes, YARN-896 is a similar scenario. Thanks for bring in that. Is there anyone currently
looking at that?
A bulk of work related to YARN-896 is done as part of Hadoop 2.6.

bq. By the way, can you provide more details about "launch a container and reuse it"? [...]
How to make the second job reuse the previous application master container?
bq. If you mean reuse the non-application-master containers, that might be possible. But for
my scenario, it needs to reuse the application master container. Is there anyway to do that?
Yes, I meant non-AM containers first. Reusing AMs should be done outside of YARN but getting
clients directly talking to the AM. Or if the 'work' being done in the AM is very little,
you can try the unmanaged AM path.

> Support in-process container executor
> -------------------------------------
>                 Key: YARN-2518
>                 URL: https://issues.apache.org/jira/browse/YARN-2518
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager
>    Affects Versions: 2.5.0
>         Environment: Linux, Windows
>            Reporter: BoYang
>            Priority: Minor
> Node Manage always creates a new process for a new application. We have hit a scenario
where we want the node manager to execute the application inside its own process, so we get
fast response time. It would be nice if Node Manager or YARN can provide native support for
> In general, the scenario is that we have a long running process which can accept requests
and process the requests inside its own process. Since YARN is good at scheduling jobs, we
want to use YARN to dispatch jobs (e.g. requests in JSON) to the long running process. In
that case, we do not want YARN container to spin up a new process for each request. Instead,
we want YARN container to send the request to the long running process for further processing.

This message was sent by Atlassian JIRA

View raw message