[
https://issues.apache.org/jira/browse/YARN-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479508#comment-13479508
]
Siddharth Seth commented on YARN-171:
-------------------------------------
I don't think this needs to be dependent on LOG_AGGREGATION_ENABLED. The NMs
can serve logs by default; if log aggregation is enabled, they route over to
the aggregated logs once aggregation completes, otherwise they serve logs till
they're available.
> NodeManager should serve logs directly if log-aggregation is not enabled
> ------------------------------------------------------------------------
>
> Key: YARN-171
> URL: https://issues.apache.org/jira/browse/YARN-171
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 0.23.3
> Reporter: Vinod Kumar Vavilapalli
>
> NodeManagers never serve logs for completed applications. If log-aggregation
> is not enabled, in the interim, due to bugs like YARN-162, this is a serious
> problem for users as logs are necessarily not available.
> We should let nodes serve logs directly if
> YarnConfiguration.LOG_AGGREGATION_ENABLED is set. This should be okay as
> NonAggregatingLogHandler can retain logs upto
> YarnConfiguration.NM_LOG_RETAIN_SECONDS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
