[YARN-10997] Revisit allocation and reservation logging

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 3.2.4, 3.3.5, 2.10.3
• Fix Version/s: 3.4.0, 3.2.4, 3.3.5, 2.10.3
• Component/s: capacity scheduler
• Labels: pull-request-available
• Target Version/s: 3.4.0, 3.2.4, 3.3.5, 2.10.3
• Hadoop Flags: Reviewed
• Assignee: Andras Gyori Assign to me
• Reporter: Andras Gyori
• Created: 02/Nov/21 06:30
• Updated: 11/Feb/24 09:55
• Resolved: 12/Nov/21 14:44

Description

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:

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>

Issue Links

• links to: GitHub Pull Request #3606