hadoop-yarn-issues mailing list archives

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

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

Wangda Tan commented on YARN-4692:
----------------------------------

[~asuresh],

Thanks for reply, I can understand your concern now.

There're two different container priorities:
- Across application container priority, this inherits application priority, and we have ACL
and/or quota ensures not everybody can claim their containers are most important.
- Container priority within an app, application can decide which container should be allocated
first and which container should be preempted first.

While doing preemption,
- For across application priority, framework should strictly enforce it.
- For priority within an application, when scheduler puts container to to-be-preempted list,
application will be notified, and it has chance to return another container other than selected.

Thoughts?

> [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
(v6.3.4#6332)

Mime
View raw message