hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7522) Abandon support for expanding ${user.name} in configs
Date Sat, 06 Aug 2011 00:51:27 GMT

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

Aaron T. Myers commented on HADOOP-7522:

Several of the default values for configuration options in Hadoop include ${user.name}, which
expands to the user name of the user running the program reading the configuration file. This
has the potential to cause subtle bugs in which different parts of the system assume that
a value is the same for all users, when in fact it may not be. For example, if the value of
{{mapred.local.dir}} includes ${user.name}, tasks will fail to launch on a secure cluster.

Additionally, some parts of Hadoop (e.g. mapreduce.jobtracker.staging.root.dir, etc) use different
methods to include the appropriate user name in a configuration value, which can confuse users.

> Abandon support for expanding ${user.name} in configs
> -----------------------------------------------------
>                 Key: HADOOP-7522
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7522
>             Project: Hadoop Common
>          Issue Type: Wish
>          Components: conf
>    Affects Versions: 0.23.0
>            Reporter: Aaron T. Myers
> In practice, I find that the presence of ${user.name} in configs is rarely helpful, and
often causes issues.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message