[
https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499191#comment-13499191
]
Robert Joseph Evans commented on YARN-162:
------------------------------------------
The patch looks good as an initial start, but I would have to dig into it more
to really understand what is happening.
In doAppLogAggregation after creating the log dir, if that fails we shut down
the file system and send an event saying the app finished but we go on trying
to aggregate the logs anyways. Also we are going to close the FileSystem later
on no matter what anyways too so it is probably unnecessary to close it here.
> nodemanager log aggregation has scaling issues with namenode
> ------------------------------------------------------------
>
> Key: YARN-162
> URL: https://issues.apache.org/jira/browse/YARN-162
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 0.23.3
> Reporter: Nathan Roberts
> Assignee: Vinod Kumar Vavilapalli
> Priority: Critical
> Attachments: YARN-162_WIP.txt
>
>
> Log aggregation causes fd explosion on the namenode. On large clusters this
> can exhaust FDs to the point where datanodes can't check-in.
--
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
