hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-896) Roll up for long lived YARN
Date Mon, 19 Aug 2013 17:33:48 GMT

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

Steve Loughran commented on YARN-896:

Chris -I use the bar today as measure of expected nodes vs actual; i.e. what percentage of
the goal of work has been met -which is free to vary up and down w/node failures -the percent
bar is free to go in both directions

YARN-1039 already says "add a flag to say long-lived", so that future versions of YARN can
behave differently. This could do more than GUI -in particular YARN-3 cgroup limits would
be something you may want to turn on for services, to exactly limit their RAM & CPU to
what they asked for. If a long-lived service underestimates its requirements the impact on
the node is worse than if a short-lived container does it -for that you may want to be more
> Roll up for long lived YARN
> ---------------------------
>                 Key: YARN-896
>                 URL: https://issues.apache.org/jira/browse/YARN-896
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            Reporter: Robert Joseph Evans
> YARN is intended to be general purpose, but it is missing some features to be able to
truly support long lived applications and long lived containers.
> This ticket is intended to
>  # discuss what is needed to support long lived processes
>  # track the resulting JIRA.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message