hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohiko Kinebuchi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8224) Don't hardcode hdfs.audit.logger in the scripts
Date Mon, 23 Apr 2012 05:03:37 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259381#comment-13259381

Tomohiko Kinebuchi commented on HADOOP-8224:

Thank you for your comment.

I created and attached a new patch including first fix and a fix for hadoop-daemon.sh.

I am thinking how do I test these fixes.

1. Kick a Hadoop cluster with this shell, and check existence of log messages in hdfs-audit.log.
2. Kick a Hadoop cluster with this shell, and get configuration values from Configuration

Do you have some other testing processes?

> Don't hardcode hdfs.audit.logger in the scripts
> -----------------------------------------------
>                 Key: HADOOP-8224
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8224
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 2.0.0
>            Reporter: Eli Collins
>            Assignee: Tomohiko Kinebuchi
>         Attachments: HADOOP-8224.txt, HADOOP-8224.txt
> The HADOOP_*OPTS defined for HDFS in hadoop-env.sh hard-code the hdfs.audit.logger (is
explicitly set via "-Dhdfs.audit.logger=INFO,RFAAUDIT") so it's not overridable. Let's allow
someone to override it as we do the other parameters by introducing HADOOP_AUDIT_LOGGER.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message