[
https://issues.apache.org/jira/browse/HADOOP-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320516#comment-14320516
]
Allen Wittenauer commented on HADOOP-11575:
-------------------------------------------
bq. Hence kept it as "Log Name" itself
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.
bq. REST
Definitely outside the scope of this JIRA. Plus, given that DFS browsing
switched to REST and broke all sorts of things that worked fine, I'm very down
on converting more stuff to REST given that negative experience.
bq. It would be really difficult to identify the required classes for
debugging and then setting them and reverting them. I was thinking more in the
lines of reloading the Log config file.
The whole point of daemonlog is for expert users to toggle various classes at
run time to enable and disable debug mode as necessary. Replacing this with a
"re-read the log4j config"-type functionality is over-engineering the problem
that this was designed to solve... never mind requiring a configuration file
change that might conflict with whatever configuration management tools are in
place. Re-reading log4j is much better suited for any of the various
reload/reconfig/refresh daemon configuration-JIRAs/functionality out there.
> 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)
