hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marco Rabozzi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4692) [Umbrella] Simplified and first-class support for services in YARN
Date Tue, 16 Feb 2016 10:19:18 GMT

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

Marco Rabozzi commented on YARN-4692:

Thanks [~vinodkv] for starting the discussion and [~asuresh] for the detailed comments on
long running container scheduling. Overall, the document gives a very detailed overview of
the current state for long running services support in YARN.

With respect to long running service upgrades, the proposal for allocation reuse (3.2.3) is
very interesting since it allows to reduce the time needed for container upgrades. However,
if the AM container is the one that needs to be upgraded, the RM should be aware of the process,
otherwise, in case of subsequent AM or NM failures the AM might be restarted with old bits.
I think that a possible solution would be to revise the design proposed in YARN-4470 to take
into account allocation reuse. We could decouple the request to update the submission context
within the RM from the actual updated *startContainer* request for the same AM allocation.

> [Umbrella] Simplified and first-class support for services in YARN
> ------------------------------------------------------------------
>                 Key: YARN-4692
>                 URL: https://issues.apache.org/jira/browse/YARN-4692
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: YARN-First-Class-And-Simplified-Support-For-Services-v0.pdf
> YARN-896 focused on getting the ball rolling on the support for services (long running
applications) on YARN.
> I’d like propose the next stage of this effort: _Simplified and first-class support
for services in YARN_.
> The chief rationale for filing a separate new JIRA is threefold:
>  - Do a fresh survey of all the things that are already implemented in the project
>  - Weave a comprehensive story around what we further need and attempt to rally the community
around a concrete end-goal, and
>  - Additionally focus on functionality that YARN-896 and friends left for higher layers
to take care of and see how much of that is better integrated into the YARN platform itself.

This message was sent by Atlassian JIRA

View raw message