[
https://issues.apache.org/jira/browse/YARN-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833488#comment-13833488
]
Zhijie Shen commented on YARN-1301:
-----------------------------------
bq. Firstly, I thought this logging should be done as DEBUG log. We can also
choose to log blacklist additions/removals as INFO or WARN. What do you think?
I think if we're going to log blacklist additions/removals every time that
allocate() is invoked, it's better to keep it at DEBUG level. Otherwise, too
many messages will be generated. Moreover, basically the log we want to add is
to help debugging.
On the other hand, if we only choose to log blacklist additions/removals when
they are not empty, we can go with INFO, while in most cases, the lists should
be empty and nothing will be logged.
> Need to log the blacklist additions/removals when YarnSchedule#allocate
> -----------------------------------------------------------------------
>
> Key: YARN-1301
> URL: https://issues.apache.org/jira/browse/YARN-1301
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Zhijie Shen
> Assignee: Tsuyoshi OZAWA
> Priority: Minor
> Fix For: 2.3.0
>
> Attachments: YARN-1301.1.patch, YARN-1301.2.patch, YARN-1301.3.patch
>
>
> Now without the log, it's hard to debug whether blacklist is updated on the
> scheduler side or not
--
This message was sent by Atlassian JIRA
(v6.1#6144)
