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

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

bq. Also, the parameter 'size' in the API 
"/containerlogs/$containerid/$filename" and similarly in AHSWebServices is 
confusing with semantics. I think we are better off with an offset and size. 
/cc Varun Vasudev. If you agree, I'll file a separate ticket.
Filed YARN-5312 for this.

> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to