[
https://issues.apache.org/jira/browse/YARN-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216047#comment-15216047
]
Jun Gong commented on YARN-4773:
--------------------------------
Thanks [~jlowe] for review, suggestion and commit!
The test case in the patch depends on YARN-4720 which is not backported to
branch 2.6 and 2.7, so I removed the test case, and updated a new patch
YARN-4773.branch-2.6.patch for 2.6 and 2.7. Is it OK?
> 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
>
> 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)
