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 "Kuhu Shukla (JIRA)" <ji...@apache.org> on 2015/09/28 21:18:04 UTC

[jira] [Assigned] (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 ]

Kuhu Shukla reassigned YARN-162:
--------------------------------

    Assignee: Kuhu Shukla  (was: Siddharth Seth)

> 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: Sub-task
>          Components: nodemanager
>    Affects Versions: 0.23.3
>            Reporter: Nathan Roberts
>            Assignee: Kuhu Shukla
>            Priority: Critical
>         Attachments: YARN-162.txt, YARN-162_WIP.txt, YARN-162_v2.txt, YARN-162_v2.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 was sent by Atlassian JIRA
(v6.3.4#6332)