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] [Resolved] (HADOOP-8464) hadoop-env.sh is included twice: once via hadoop-config.sh the again explicitly via scripts
Date Mon, 09 Mar 2015 15:47:39 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer resolved HADOOP-8464.
--------------------------------------
    Resolution: Duplicate

Duping this to HADOOP-9902 which fixed this.

> hadoop-env.sh is included twice: once via hadoop-config.sh the again explicitly via scripts
> -------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8464
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8464
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 2.0.0-alpha
>            Reporter: Jay Finger
>
> Many (most? all?) scripts include hadoop-env.sh twice.  The first time is indirectly:
 scripts do ". hadoop-config.sh" and hadoop-config.sh then does ". hadoop-env.sh".  Then scripts
will later directly do ". hadoop-env.sh".
> This double-include is error prone.
> Note several Jira's reporting issues with HADOOP_LOG_DIR set to /user/user (e.g. /root/root,
/hadoop/hadop, etc).  This is because hadoop-env.sh has done "HADOOP_LOG_DIR=$HADOOP_LOG_DIR/$user".
 Many fixes for those issues are around addressing that one line, but it seems that this is
going to be a recurring theme of breakages.  It's probably also why services are routinely
started with many command line arguments repeated multiple times.
> I'm not familiar enough with the "design" of all the scripts, so not sure what the solution
should be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message