hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-8479) The capacity scheduler logs too frequently seriously affecting performance
Date Fri, 29 Jun 2018 09:56:00 GMT

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

Weiwei Yang commented on YARN-8479:

Hi [~daemon]

In my opinion, reduce the verbose of logs makes sense, but this is not saying we should move
all INFO to DEBUG. For users don't have such strict perf request, they could still use INFO
level; for users require high perf, then turn it to WARN. Fix those most frequently printing
(repeat) logs will be very helpful.

> The capacity scheduler logs too frequently seriously affecting performance
> --------------------------------------------------------------------------
>                 Key: YARN-8479
>                 URL: https://issues.apache.org/jira/browse/YARN-8479
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler, capacityscheduler
>            Reporter: YunFan Zhou
>            Assignee: YunFan Zhou
>            Priority: Critical
>         Attachments: image-2018-06-29-14-16-06-332.png
> The capacity scheduler logs too frequently, seriously affecting performance.
> As a result of our test that the scheduling speed of capacity scheduler is difficult
to reach 5000/s in the production scenario.
> And it will soon reach the log bottleneck.
> My current work is to change many log levels from INFO to DEBUG level.
> [~wangda] [~leftnoteasy] Any suggestion?
> !image-2018-06-29-14-16-06-332.png!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message