You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2012/11/16 21:57:12 UTC
[jira] [Updated] (YARN-162) nodemanager log aggregation has scaling
issues with namenode
[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated YARN-162:
--------------------------------
Attachment: YARN-162_WIP.txt
Work in progress patch for YARN-219, YARN-220.
Is a reasonably simple change - the aggregator thread for an app is started after the app completes, the aggregator takes care of directory creation and there's a limited number of threads for aggregation.
> 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