You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2013/09/02 09:19:51 UTC
[jira] [Created] (YARN-1135) Revisit log message levels in
FairScheduler.
Alejandro Abdelnur created YARN-1135:
----------------------------------------
Summary: Revisit log message levels in FairScheduler.
Key: YARN-1135
URL: https://issues.apache.org/jira/browse/YARN-1135
Project: Hadoop YARN
Issue Type: Bug
Components: scheduler
Affects Versions: 2.1.0-beta
Reporter: Alejandro Abdelnur
Assignee: Sandy Ryza
Fix For: 2.1.1-beta
FairScheduler produces allocation attempts at INFO level, those should be a DEBUG level:
{code}
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
...
{code}
We should curate all log message levels
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira