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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/03/09 17:14:41 UTC

[jira] [Assigned] (YARN-4773) Log aggregation performs extraneous filesystem operations when rolling log aggregation is disabled

     [ https://issues.apache.org/jira/browse/YARN-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe reassigned YARN-4773:
--------------------------------

    Assignee: Jun Gong

Feel free, as I'm currently busy with other tasks.  I filed it and left it unassigned in the hope someone in the community would have the time to pick it up, so thanks!

> Log aggregation performs extraneous filesystem operations when rolling log aggregation is disabled
> --------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4773
>                 URL: https://issues.apache.org/jira/browse/YARN-4773
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Jun Gong
>            Priority: Minor
>
> I noticed when log aggregation occurs for an application the nodemanager is listing the application's log directory in HDFS.  Apparently this is for removing old logs before uploading new ones.  This is a wasteful operation when rolling log aggregation is disabled, since there will be no prior logs in HDFS -- aggregation only occurs once when rolling log aggregation is disabled.



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