hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3336) hdfs launcher script will be better off not special casing namenode command with regards to hadoop.security.logger
Date Wed, 02 May 2012 23:28:01 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267020#comment-13267020
] 

Hudson commented on HDFS-3336:
------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #2249 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2249/])
    HDFS-3336. hdfs launcher script will be better off not special casing namenode command
with regards to hadoop.security.logger (rvs via tucu) (Revision 1333236)

     Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333236
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs

                
> 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
>
>         Attachments: HDFS-3336.patch.txt
>
>
> 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

        

Mime
View raw message