[
https://issues.apache.org/jira/browse/HADOOP-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naganarasimha G R updated HADOOP-11575:
---------------------------------------
Attachment: HADOOP-11575.20150213-2.patch
Hi Allen Wittenauer,
Initially even i was thinking about the same, but in log4j terms they call it
as log itself and interface definitions also finally narrow down to
{{LogFactory.getLog(String name)}}
Also in some places in the code they have used the log created from one class
name is used in other classes also . For instance Log in the NameNode class is
used in many other classes and one such class being :
DatanodeManager.registerDatanode
bq. NameNode.LOG.info("BLOCK* registerDatanode: " + nodeN);
Hence kept it as "Log Name" itself
bq. Back ticks. See Federation.md and search for dfsclusterheatlth.jsp for an
example.
Thanks for sharing, have updated it in the latest patch
Hi [~wheat9],
bq. Should we consider deprecating this servlet and provide a REST API instead?
IIUC in this case we need to have a REST mapping in each of the daemon service
for getting or setting log level,
and existing servlet approach seems to be simple approach and if really required
then would not mind to work on it. Also is it required as part of this jira?
Also i was thinking about the usability of this daemonlog. 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.
so that users can modify the log4j and call a similar servlet which can
dynamically reload the log4j config.
If this Idea is good then will check the feasibility and raise a jira for it
> 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)
