Uploaded image for project: 'CDH (READ-ONLY)'
  1. CDH (READ-ONLY)
  2. DISTRO-235

conf-pseudo inconsistent about HDFS dir names

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: CDH3u0
    • Fix Version/s: CDH4b2
    • Component/s: HDFS, Packaging
    • Labels:
      None

      Description

      conf-pseudo contains the following in hdfs-site.xml and core-site.xml:

        <property>
           <!-- specify this so that running 'hadoop namenode -format' formats the right dir -->
           <name>dfs.name.dir</name>
           <value>/var/lib/hadoop-0.20/cache/hadoop/dfs/name</value>
        </property
      
        <property>
           <name>hadoop.tmp.dir</name>
           <value>/var/lib/hadoop-0.20/cache/${user.name}</value>
        </property>
      

      And inherits:

      <property>
        <name>fs.checkpoint.dir</name>
        <value>${hadoop.tmp.dir}/dfs/namesecondary</value>
        <description>Determines where on the local filesystem the DFS secondary
            name node should store the temporary images to merge.
            If this is a comma-delimited list of directories then the image is
            replicated in all of the directories for redundancy.
        </description>
      </property>
      

      What this means, I believe, is that the SNN and the NN come up with fairly different paths:

      • /var/lib/hadoop-0.20/cache/hdfs/dfs/namesecondary
      • /var/lib/hadoop-0.20/cache/hadoop/dfs/name

      They should either both be cache/hdfs or both be cache/hadoop.

      Note that I tested this by using the conf.pseudo from the tarballs; I haven't double-checked that the same thing is happening when using the conf-pseudo package.

        Attachments

          Activity

            People

            • Assignee:
              rvs Roman V Shaposhnik
              Reporter:
              philip Philip Zeyliger
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: