[
https://issues.apache.org/jira/browse/HADOOP-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316918#comment-14316918
]
Naganarasimha G R commented on HADOOP-11575:
--------------------------------------------
bq. Not a fan of this verbage. I prefer man page style where it is mainly:
May be i dint convey it correctly, At present {{-getlevel <host:httpPort>
{color:red}<name> .{color} }} is getting displayed in CLI as usage and was
planning to do it as {{-getlevel <host:httpPort> {color:red}<log name> .{color}
}}
And for documentation will update it at the earliest and share the patch
{quote}
a) If a user defines a custom level, what happens?
b) What if there is more than just case conversion happening, especially in a
i18n capacity?
{quote}
Well IIUC, org.apache.log4j.Level.toLevel(level) supports for only the default
types Log4j supports(ALL,DEBUG,INFO,WARN,ERROR,FATAL,OFF,TRACE) and if none of
the string matches then selects DEBUG as default.
Ok if its for sake of uniformity we can keep it as Upper case itself but
earlier thought that it would be easier for user to either give in upper case
or lower case.
> Daemon log documentation is misleading
> --------------------------------------
>
> Key: HADOOP-11575
> URL: https://issues.apache.org/jira/browse/HADOOP-11575
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Reporter: Jagadesh Kiran N
> Assignee: Naganarasimha G R
>
> a. Execute the command
> ./yarn daemonlog -setlevel xx.xx.xx.xxx:45020 ResourceManager DEBUG
> b. It is not reflecting in process logs even after performing client level
> operations
> c. Log level is not changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
