hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4541) set hadoop.log.dir and hadoop.id.str when starting secure datanode so it writes the logs to the correct dir by default
Date Fri, 01 Mar 2013 18:49:12 GMT

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

Arpit Gupta commented on HDFS-4541:
-----------------------------------

@Chris

Actually it will appear 3 times after this change for secure datanode. It appears twice for
any hdfs service right now.

hadoop-deamon.sh -> hadoop (sources hadoop-config.sh) -> hdfs (source hdfs-config.sh
which sources hadoop-config.sh) and then we set it again.

I think the problem of duplicates in OPTS is a an issue that should be solved in a different
jira.
                
> set hadoop.log.dir and hadoop.id.str when starting secure datanode so it writes the logs
to the correct dir by default
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4541
>                 URL: https://issues.apache.org/jira/browse/HDFS-4541
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, security
>    Affects Versions: 2.0.3-alpha
>            Reporter: Arpit Gupta
>            Assignee: Arpit Gupta
>         Attachments: HDFS-4541.patch, HDFS-4541.patch
>
>
> currently in hadoop-config.sh we set the following
> {code}
> HADOOP_OPTS="$HADOOP_OPTS -Dhadoop.log.dir=$HADOOP_LOG_DIR"
> HADOOP_OPTS="$HADOOP_OPTS -Dhadoop.id.str=$HADOOP_IDENT_STRING"
> {code}
> however when this file is sourced we dont know whether we are starting a secure data
node.
> In the hdfs script when we determine whether we are starting secure data node or not
we should also update HADOOP_OPTS

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message