[
https://issues.apache.org/jira/browse/YARN-8479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527488#comment-16527488
]
YunFan Zhou commented on YARN-8479:
-----------------------------------
Thank [~cheersyang]
I totally agree with you and it's really hard to make this completely generic.
According to our experience, we can change below log level from INFO to DEBUG:
||Class Name||Method Name||The number of logs in proportion||
|rmcontainer.RMContainerImpl|handle|37.7%|
|scheduler.SchedulerNode|releaseContainer|9.3%|
|scheduler.SchedulerNode|allocateContainer|9.3%|
|resourcemanager.RMAuditLogger|logSuccess|19.0%|
|allocator.AbstractContainerAllocator| getCSAssignmentFromAllocateResult| 14.1%|
| capacity.CapacityScheduler| allocateContainerOnSingleNode| 4.4%|
In this way, we can reduce the total amount of logs to previous ones' 6.2% and
which can improve RM's performance to a large extent.
According to our experience in production, it can improve scheduling
performance by 30%-50%.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
