hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-448) Remove unnecessary hflush from log aggregation
Date Mon, 04 Mar 2013 18:51:12 GMT

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

Kihwal Lee commented on YARN-448:
---------------------------------

Test not included since it does not affect normal cases. Even in failure cases, no current
error handling in log aggregation is affected by the existence or absence of version record
in a log that failed during aggregation.
                
> Remove unnecessary hflush from log aggregation
> ----------------------------------------------
>
>                 Key: YARN-448
>                 URL: https://issues.apache.org/jira/browse/YARN-448
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 0.23.7, 2.0.4-beta
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>         Attachments: yarn-448.patch.txt
>
>
> AggregatedLogFormat#writeVersion() calls hflush() after writing the version. Calling
hflush does not seem to be necessary. It can add a lot of load to hdfs in a big busy cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message