[
https://issues.apache.org/jira/browse/HADOOP-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320531#comment-14320531
]
Naganarasimha G R commented on HADOOP-11575:
--------------------------------------------
bq. I guess the problem I have with log name is that it indicates that one
should be passing a filename and not a class. I think users might get confused.
On the flip side, messing with daemonlog should really be considered 'advanced'
or 'expert' level controls.
So to conclude shall change it in all places to "Class Name" ?
bq. Re-reading log4j is much better suited for any of the various
reload/reconfig/refresh daemon configuration-JIRAs/functionality out there.
Ok.
> 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
> Attachments: CommandsManual.html, HADOOP-11575.20150213-1.patch,
> HADOOP-11575.20150213-2.patch, YarnCommands.html
>
>
> 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)
