You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2016/07/05 18:12:11 UTC
[jira] [Commented] (YARN-5224) Logs for a completed container are
not available in the yarn logs output for a live application
[ https://issues.apache.org/jira/browse/YARN-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362901#comment-15362901 ]
Vinod Kumar Vavilapalli commented on YARN-5224:
-----------------------------------------------
The latest patch looks good to me. Some of the checkstyle warnings can be addressed? TestLogsCLI failure is related to recent changes?
> 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
> Attachments: YARN-5224.1.patch, YARN-5224.2.patch, YARN-5224.3.patch, YARN-5224.4.patch, YARN-5224.5.patch, YARN-5224.6.patch, YARN-5224.6.trunk.patch, YARN-5224.7.trunk.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