Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-4963

Improve multihoming support in namenode

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1-win, 1.3.0
    • Component/s: namenode
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      HDFS does not work very well on multi-homed machines. A few open Jiras refer to this:

      1. HDFS-1379
      2. HADOOP-8198

      There are multiple issues involved here and some of them can be worked around by using alternate DNS names and configuring slave.host.name on Datanodes and task trackers.

      However namenode issues cannot be worked around because it does not respect the fs.default.name configuration. e.g. Namenode#initialize performs a gratuitous reverse DNS lookup to regenerate the hostname. Similar issues exist elsewhere.

      This Jira is being filed to fix some of the more serious problems. To avoid affecting existing users a new config setting may be introduced.

        Attachments

        1. HDFS-4963.branch-1.patch
          35 kB
          Arpit Agarwal
        2. HDFS-4963.branch-1.001.patch
          36 kB
          Arpit Agarwal
        3. HDFS-4963.branch-1.002.patch
          36 kB
          Arpit Agarwal

          Activity

            People

            • Assignee:
              arp Arpit Agarwal
              Reporter:
              arp Arpit Agarwal
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: