hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hung (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4969) Fix more loggings in CapacityScheduler
Date Thu, 27 Oct 2016 18:56:59 GMT

     [ https://issues.apache.org/jira/browse/YARN-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hung updated YARN-4969:
--------------------------------
    Labels: oct16-easy  (was: )

> Fix more loggings in CapacityScheduler
> --------------------------------------
>
>                 Key: YARN-4969
>                 URL: https://issues.apache.org/jira/browse/YARN-4969
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacity scheduler
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>              Labels: oct16-easy
>         Attachments: YARN-4969.1.patch
>
>
> 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)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message