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/04/05 16:06:25 UTC

[jira] [Updated] (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 updated YARN-4773:
-----------------------------
    Fix Version/s: 2.6.5
                   2.7.3

Apologies for the long delay.

+1 for the branch-2.6 patch.  Thanks, Jun!  I committed it to branch-2.7 and branch-2.6.  


> 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
>             Fix For: 2.8.0, 2.7.3, 2.6.5
>
>         Attachments: YARN-4773-branch-2.6.patch, YARN-4773.01.patch, YARN-4773.02.patch, YARN-4773.03.patch
>
>
> 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)