[
https://issues.apache.org/jira/browse/HDFS-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943038#comment-14943038
]
Vinayakumar B commented on HDFS-9114:
-------------------------------------
1. I feel, you can also add one more env variable to define the metrics logger
, similar to HDFS_AUDIT_LOGGER
2. Also these env variables needs to be updated (commented) in hadoop-env.sh
and hadoop-env.cmd
3. You might need to update hdfs.cmd as well to support this in windows
4. You can set default logger to NullAppender for tests as well as these
metrics outputs are not verified from the file in tests. There will be one more
appender added in tests. Currently there is no NullAppender in test's log4j,
you can add the following entry.
{code}
# Null Appender
log4j.appender.NullAppender=org.apache.log4j.varia.NullAppender
{code}
> NameNode and DataNode metric log file name should follow the other log file
> name format.
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-9114
> URL: https://issues.apache.org/jira/browse/HDFS-9114
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Attachments: HDFS-9114-branch-2.01.patch,
> HDFS-9114-branch-2.02.patch, HDFS-9114-trunk.01.patch,
> HDFS-9114-trunk.02.patch
>
>
> Currently datanode and namenode metric log file name is
> {{datanode-metrics.log}} and {{namenode-metrics.log}}.
> This file name should be like {{hadoop-hdfs-namenode-metric-host192.log}}
> same as namenode log file {{hadoop-hdfs-namenode-host192.log}}.
> This will help when we will copy log for issue analysis from different node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
