[
https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15914204#comment-15914204
]
Junping Du commented on YARN-6313:
----------------------------------
This feature/improvement is very useful when we debugging a running application
with container failures. We can figure out the reason by getting related log
without waiting for application finish (for long running service, it may never
finish).
The patch looks good in over all, only one NIT:
{noformat}
+ System.err.println("Unable to get logs for this container:"
+ + containerIdStr + "for the application:" + appIdStr
+ + " with the appOwner: " + appOwner);
{noformat}
We should have space between containerIdStr and "for the application".
Other looks fine to me.
> yarn logs cli does not provide logs for a completed container even when the
> nm address is provided
> --------------------------------------------------------------------------------------------------
>
> Key: YARN-6313
> URL: https://issues.apache.org/jira/browse/YARN-6313
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Xuan Gong
> Attachments: YARN-6313.1.patch
>
>
> Running app. Completed container.
> Provide the appId, containerId, nodeId - yarn logs does not return the logs.
> Specific use case: Long Running app. One daemon crashed. Logs are not
> accessible without shutting down the app.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
