[
https://issues.apache.org/jira/browse/YARN-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula updated YARN-4969:
---------------------------------------
Target Version/s: 3.4.0 (was: 3.3.0)
Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a
blocker.
> Fix more loggings in CapacityScheduler
> --------------------------------------
>
> Key: YARN-4969
> URL: https://issues.apache.org/jira/browse/YARN-4969
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Major
> Labels: oct16-easy
> Attachments: YARN-4969.1.patch
>
>
> YARN-3966 did logging cleanup for Capacity Scheduler before, however,
> there're some loggings we need to improvement:
> Container allocation / complete / reservation / un-reserve messages for every
> hierarchy (app/leaf/parent-queue) should be printed at INFO level:
> I'm debugging one issue that root queue's resource usage could be negative,
> it is very hard to reproduce, so we cannot enable debug logging since RM
> start, size of log cannot be fit in a single disk.
> Existing CS prints INFO message when container cannot be allocated, such as
> re-reservation / node heartbeat, etc. we should avoid printing such message
> at INFO level.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
