Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> [jira] [Created] (HADOOP-10329) Fully qualified URIs are inconsistant and sometimes break in hadoop conf files


Copy link to this message
-
[jira] [Created] (HADOOP-10329) Fully qualified URIs are inconsistant and sometimes break in hadoop conf files
Travis Thompson created HADOOP-10329:
----------------------------------------

             Summary: Fully qualified URIs are inconsistant and sometimes break in hadoop conf files
                 Key: HADOOP-10329
                 URL: https://issues.apache.org/jira/browse/HADOOP-10329
             Project: Hadoop Common
          Issue Type: Bug
          Components: conf
    Affects Versions: 2.2.0
            Reporter: Travis Thompson
When specifying paths in the *-site.xml files, some are required to be fully qualified, while others (specifically hadoop.tmp.dir) break when a fully qualified uri is used.

Example:
If I set hadoop.tmp.dir in core-site to file:///something it'll create a file: directory in my $PWD.
{noformat}
  <property>
    <name>hadoop.tmp.dir</name>
    <value>file:///grid/a/tmp/hadoop-${user.name}</value>
  </property>
{noformat}
{noformat}
[tthompso@test ~]$ tree file\:/
file:/
└── grid
    └── a
        └── tmp
            └── hadoop-tthompso
{noformat}

Other places, like the datanode, or the nodemanager, will complain if I don't use fully qualified uris
{noformat}
  <property>
    <name>dfs.datanode.data.dir</name>
    <value>/grid/a/dfs-data/bs</value>
  </property>
{noformat}
{noformat}
WARN org.apache.hadoop.hdfs.server.common.Util: Path /grid/a/dfs-data/bs should be specified as a URI in configuration files. Please update hdfs configuration.
{noformat}

--
This message was sent by Atlassian JIRA
(v6.1.5#6160)