You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2016/04/20 01:09:25 UTC

[jira] [Created] (YARN-4969) Fix more loggings in CapacityScheduler

Wangda Tan created YARN-4969:
--------------------------------

             Summary: Fix more loggings in CapacityScheduler
                 Key: YARN-4969
                 URL: https://issues.apache.org/jira/browse/YARN-4969
             Project: Hadoop YARN
          Issue Type: Bug
          Components: capacity scheduler
            Reporter: Wangda Tan
            Assignee: Wangda Tan


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
(v6.3.4#6332)