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

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

bq. We could still get the logs if the container logs still exist in NM Local 
log directory even if we remove container from NMContext.
bq. To solve this issue, we need to create a separate NMWebService to get log 
name of the container. 
Instead of a completely new path you added - 
{{"/containerlogs/container/$containerid$/logfiles"}}, the following would be 
more consistent
 - Existing {{"/containers/$containerid"}} returns container-info (and the list 
of containerLogFiles inside the info)
 - New {{"/containers/$containerid/logs"}} returns names of the log-files, and 
may be simple metadata like size of log-file etc
 - Existing logs-webservice should have been 
{{"/containerlogs/$containerid/$filename"}} -> 
{{"/containers/$containerid$/logs/$filename"}} returns contents. Obviously we 
cannot remove the old API, as it is public.

The nice thing is this is the same pattern that the UI flow also follows.

/cc [~vvasudev]

> 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
>
>
> 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