Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 23 Jul 2013 20:30:50 +0000 (UTC)
From: "Thomas Weise (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12655952.1372813766822.99345.1374611450746@arcas>
In-Reply-To: <JIRA.12655952.1372813766822@arcas>
References: <JIRA.12655952.1372813766822@arcas>
Subject: [jira] [Commented] (YARN-896) Roll up for long lived YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Weise commented on YARN-896:
-----------------------------------

[~revans2] Applications may connect to other services such as HBase or issue tokens for communication between its own containers. All of these would require renewal.

                
> 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