hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13040) HADOOP_NAMENODE_OPTS does not pass -DconfigKey=Value to namenode as parameter
Date Thu, 21 Apr 2016 00:28:28 GMT

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

Allen Wittenauer commented on HADOOP-13040:

Yup, that sounds like a bug in Configuration.  It's kind of odd though, given that at least
a null value for hadoop.security.group.mapping.ldap.bind.password.file should be coming from
the core-default.xml file bundled in the jar though.   But whatever.  There have been a lot
of changes in that part of code since the "interface" of using system properties to pass config
info was set up eons ago.  It's gotten significantly complicated enough that breakages like
this shouldn't be too surprising.

Anyway, I'll let you update the JIRA issue to reflect reality, since this isn't a script bug.
:)  Thanks.

> HADOOP_NAMENODE_OPTS does not pass -DconfigKey=Value to namenode as parameter 
> ------------------------------------------------------------------------------
>                 Key: HADOOP-13040
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13040
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
> We want to hide the ldap bind password file path from core-site.xml by setting the following
in hadoop-env.sh only.
> export HADOOP_NAMENODE_OPTS=$HADOOP_NAMENODE_OPTS -Dhadoop.security.group.mapping.ldap.bind.password.file
> However, it does not work as expected and the BIND_PASSWORD_FILE_PATH is not honored
with existing hadoop_add_param call from hadoop-config.sh/hadoop-function.sh.

This message was sent by Atlassian JIRA

View raw message