[
https://issues.apache.org/jira/browse/HADOOP-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316417#comment-14316417
]
Allen Wittenauer commented on HADOOP-11575:
-------------------------------------------
bq. whether we can update document for YARN and Hadoop common in the same jira
Go for it.
bq. I feel daemonlog usage can be updated
bq. General options are:
Not a fan of this verbage. I prefer man page style where it is mainly:
{code}
Usage:
xyz daemonlog optionset1
xyz daemonlog optionset2
{code}
bq. Level.toLevel(string) takes care of appropriate case conversions
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?
> 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)
