hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-896) Roll up for long-lived services in YARN
Date Tue, 03 Feb 2015 19:23:44 GMT

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

Vinod Kumar Vavilapalli commented on YARN-896:
----------------------------------------------

bq. I created a jira YARN-3130 for excessive progress report logs in application master. I
think the log issue is very important for a long running service in YARN. Should YARN-3130
be linked to this JIRA?
Tx for filing YARN-3130. I am moving it to MapReduce project. I think it is orthogonal to
this JIRA, so we can keep it separate.

> Roll up for long-lived services in 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message