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 "Hong Zhiguo (JIRA)" <ji...@apache.org> on 2015/07/08 12:37:05 UTC

[jira] [Commented] (YARN-3897) "Too many links" in NM log dir

    [ https://issues.apache.org/jira/browse/YARN-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618365#comment-14618365 ] 

Hong Zhiguo commented on YARN-3897:
-----------------------------------

One solution is to have an extra layer of dirs as the parent of "appId" subdirs.  The middle layer of dirs could be named with hash of appId. 
This behaviour shoud be configrable.

> "Too many links" in NM log dir
> ------------------------------
>
>                 Key: YARN-3897
>                 URL: https://issues.apache.org/jira/browse/YARN-3897
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Hong Zhiguo
>            Assignee: Hong Zhiguo
>            Priority: Minor
>
> Users need to left container logs more than one day. On some nodes of our busy cluster, the number of subdirs of {yarn.nodemanager.log-dirs} may reach 32000, which is the defaul limit of ext3 file system. As a result, we got errors when initiating containers:
> "Failed to create directory {yarn.nodemanager.log-dirs}/logs/application_1435111082717_1341740 - Too many links"
> log aggregation is not an option for us because of the heavy pressure on namenode. With a cluster of 5K nodes and 20k log files per node, it's not acceptable to aggregate so many files to hdfs.
> Since ext3 is still widely used, we'd better do something to avoid such error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)