[HDFS-3336] hdfs launcher script will be better off not special casing namenode command with regards to hadoop.security.logger

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.23.1
• Fix Version/s: 2.0.0-alpha
• Component/s: scripts
• Hadoop Flags: Reviewed
• Assignee: Roman Shaposhnik
• Reporter: Roman Shaposhnik
• Created: 01/May/12 16:27
• Updated: 28/Sep/15 20:58
• Resolved: 02/May/12 22:48

Description

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.