[
https://issues.apache.org/jira/browse/YARN-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623902#comment-15623902
]
Naganarasimha G R commented on YARN-5810:
-----------------------------------------
IIUC i believe this is little tricky, though we ensure all the classes to have
{{LoggerFactory.getLogger(<class>);}}, getLogger is overloaded to accept String
too, so we can pass anything as the name of the logger due to which currently
we are accepting any string. So to enforce "RM Loglevel setting shouldn't
return a valid value for a non-existing class", we should go by the assumption
that Logger name is always set as classname.
Other disadvantage being, later might be we can plan to change the logger name
to match a group of classes (or have it as the package name), so that we need
not manually modify the log level of individual classes.
Thoughts ?
> RM Loglevel setting shouldn't return a valid value for a non-existing class
> ---------------------------------------------------------------------------
>
> Key: YARN-5810
> URL: https://issues.apache.org/jira/browse/YARN-5810
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.0.0-alpha1
> Reporter: Yufei Gu
> Assignee: Yufei Gu
>
> The WebUI of RM Loglevel setting should not return a valid value, like INFO
> for an non-existing class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
