[
https://issues.apache.org/jira/browse/HADOOP-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315204#comment-14315204
]
Naganarasimha G R commented on HADOOP-11575:
--------------------------------------------
Hi [~aw],
Thanks for moving but i had few queries:
# whether we can update document for YARN and Hadoop common in the same jira
as daemon log is documented separately for
[Hadoop|http://hadoop.apache.org/docs/r2.6.0/hadoop-project-dist/hadoop-common/CommandsManual.html#daemonlog]
and
[YARN|http://hadoop.apache.org/docs/r2.6.0/hadoop-yarn/hadoop-yarn-site/YarnCommands.html#daemonlog],
# I feel daemonlog usage can be updated as i mentioned earlier, please
provide your opinion on this
{quote}
Usage: General options are:
[-getlevel <host:httpPort> <log name>]
[-setlevel <host:httpPort> <log name> <level>]
{quote}
# ??These levels are defined by log4j and defined as uppercase everywhere in
both code and config. Making it mixed case here means supporting mixed case
everywhere...??
ok, I mentioned this because, its failing at the validation done @ the servlet
level and Level.toLevel(string) takes care of appropriate case conversions.
{quote}
if (!level.equals(org.apache.log4j.Level.toLevel(level).toString())) {
out.println(MARKER + "Bad level : <b>" + level + "</b><br />");
} else {
{quote}
> 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)
