[YARN-1135] Revisit log message levels in FairScheduler.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.1.0-beta
• Fix Version/s: 2.1.1-beta
• Component/s: scheduler
• Assignee: Karthik Kambatla
• Reporter: Alejandro Abdelnur
• Created: 02/Sep/13 07:17
• Updated: 03/Nov/14 18:06
• Resolved: 02/Sep/13 18:44

Description

FairScheduler produces allocation attempts at INFO level, those should be a DEBUG level:

2013-09-02 09:14:47,815 INFO  [ResourceManager Event Processor] fair.AppSchedulable (AppSchedulable.java:assignContainer(277)) - Node offered to app: application_1378106082360_0001 reserved: false
2013-09-02 09:14:47,815 INFO  [ResourceManager Event Processor] fair.AppSchedulable (AppSchedulable.java:assignContainer(277)) - Node offered to app: application_1378106082360_0002 reserved: false
2013-09-02 09:14:48,247 INFO  [ResourceManager Event Processor] fair.AppSchedulable (AppSchedulable.java:assignContainer(277)) - Node offered to app: application_1378106082360_0001 reserved: false
...

We should curate all log message levels

Issue Links

• is duplicated by: YARN-305 Fair scheduler logs too many "Node offered to app:..." messages