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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/10/17 20:20:05 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13478098#comment-13478098 ] 

Vinod Kumar Vavilapalli commented on YARN-162:
----------------------------------------------

Pity we didn't foresee this.

The NM has per-app file handles open, but it doesn't close them till the application finishes.

Arguably, this connections are to the data-nodes, but the DFSClient also keeps a transient connection to NNs which seem to be causing this.

Will investigate more and take a stab at fixing this.
                
> 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
>
> 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