hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-896) Roll up for long lived YARN
Date Tue, 30 Jul 2013 15:43:53 GMT

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

Siddharth Seth commented on YARN-896:

bq. Robert Joseph Evans Applications may connect to other services such as HBase or issue
tokens for communication between its own containers. All of these would require renewal.
The RM takes care of renewing tokens for HDFS - it can do this since the HDFS token renewer
class is in the RM's classpath. For other applications - Hive for example - this isn't possible.
I believe Hive ends up issuing tokens which are valid for a longer duration to get around
the renewal problem. I won't necessarily link this to long running YARN though - other than
the bit about the token max-age.
> 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