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-5224) Logs for a completed container are not available in the yarn logs output for a live application
Date Tue, 21 Jun 2016 01:22:58 GMT

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

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

bq. Marking this as incompatible since the patch includes RESTful API's endpoint change
[~ozawa], the patch is not deleting or renaming the API, it is adding a new API leaving the
old one behind for deprecation. It's a compatible change.

> Logs for a completed container are not available in the yarn logs output for a live application
> -----------------------------------------------------------------------------------------------
>
>                 Key: YARN-5224
>                 URL: https://issues.apache.org/jira/browse/YARN-5224
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.9.0
>            Reporter: Siddharth Seth
>            Assignee: Xuan Gong
>              Labels: incompatible
>         Attachments: YARN-5224.1.patch, YARN-5224.2.patch, YARN-5224.3.patch, YARN-5224.4.patch,
YARN-5224.5.patch
>
>
> This affects 'short' jobs like MapReduce and Tez more than long running apps.
> Related: YARN-5193 (but that only covers long running apps)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message