[
https://issues.apache.org/jira/browse/YARN-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185401#comment-15185401
]
Ming Ma commented on YARN-4773:
-------------------------------
[~jlowe], can you please confirm if it has been fixed by YARN-4720 which has
removed the extra {{remoteFS.exists(remoteNodeTmpLogFileForApp)}} for all log
aggregation scenarios.
> 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
> 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)
