Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 19 Aug 2013 13:46:04 +0000 (UTC)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12655952.1372813766822.89730.1376919964489@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=13743819#comment-13743819 ] 

Robert Joseph Evans commented on YARN-896:
------------------------------------------

[~criccomini],

That is a great point.  To do this we need the application to somehow inform YARN that it is a long lived application.  We could do this either through some sort of metadata that is submitted with the application to YARN, possibly through the service registry, or even perhaps just setting the progress to a special value like -1.  I think I would prefer the first one, because then YARN could use that metadata later on for other things.  After that the UI change should not be too difficult.  If you want to file a JIRA for it, either as a sub task or just link it in, that would be great.
                
> 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