Roman Shaposhnik created HDFS-3336:
--------------------------------------
Summary: hdfs launcher script will be better off not special
casing namenode command with regards to hadoop.security.logger
Key: HDFS-3336
URL: https://issues.apache.org/jira/browse/HDFS-3336
Project: Hadoop HDFS
Issue Type: Bug
Components: scripts
Affects Versions: 0.23.1
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik
Priority: Minor
Fix For: 2.0.0
All of the launcher scripts (except hdfs when called with a namenode argument)
are defaulting to INFO,NullAppender setting for hadoop.security.logger. The
only codepath where the default is INFO,RFAS is via hadoop-daemon.sh. This is
exactly the right thing to do since only daemons are guaranteed to be executed
under the proper user account (the one that has write/create access to the
locations specified in ${hadoop.log.dir}/*).
It would be nice for 'hdfs namenode' to follow the suit and not produce
spurious warnings about not being able to write to log locations when executed
from under regular accounts.
--
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
