[
https://issues.apache.org/jira/browse/YARN-10997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Payne updated YARN-10997:
------------------------------
Fix Version/s: 3.2.4
3.3.9
2.10.3
> Revisit allocation and reservation logging
> ------------------------------------------
>
> Key: YARN-10997
> URL: https://issues.apache.org/jira/browse/YARN-10997
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Andras Gyori
> Assignee: Andras Gyori
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.9, 2.10.3
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Accepted allocation proposal and reserved container logs are two exceedingly
> frequent events. Numerous user reported that these log entries had quickly
> filled the logs on a busy cluster and seen these entries only as noise.
> It would be worthwhile to reduce the log level of these entries to DEBUG
> level.
> Examples:
> {noformat}
> 2021-10-30 02:28:57,409 INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler:
> Allocation proposal accepted
> 2021-10-30 02:28:57,439 INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.common.fica.FiCaSchedulerApp:
> Reserved container=container_1635478503131_0069_01_000078, on node=host:
> node:8041 #containers=1 available=<memory:1835, vCores:3> used=<memory:3072,
> vCores:1> with resource=<memory:3072, vCores:1>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
