hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1291) RM INFO logs limit scheduling speed
Date Mon, 28 Jul 2014 10:14:39 GMT

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

Varun Saxena commented on YARN-1291:

Hi [~sandyr], I had raised YARN-2287 which is also about printing of too many RM Audit logs
in critical flow. For this, in the patch, I had added support for printing audit logs at different
log levels and changed container logs in RM and NM to DEBUG. I didnt remove the audit logs
as I wasnt sure if these audit logs are really required or not.  

> RM INFO logs limit scheduling speed
> -----------------------------------
>                 Key: YARN-1291
>                 URL: https://issues.apache.org/jira/browse/YARN-1291
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.2.0
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
> I've been running some microbenchmarks to see how fast the Fair Scheduler can fill up
a cluster and found its performance is significantly hampered by logging.
> I tested with 500 (mock) nodes, and found that:
> * Taking out fair scheduler INFO logs on the critical path brought down the latency from
14000 ms to 6000 ms
> * Taking out the INFO that RMContainerImpl logs when a container transitions brought
it down from 6000 ms to 4000 ms
> * Taking out RMAuditLogger logs brought it down from 4000 ms to 1700 ms

This message was sent by Atlassian JIRA

View raw message