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

Add a separate configuration for namenode rpc address instead of only using fs.default.name

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.0, 2.1.1-beta, 3.0.0-alpha1
    • Fix Version/s: 1.2.0
    • Component/s: datanode, namenode
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      The namenode RPC address is currently identified from configuration "fs.default.name". In some setups where default FS is other than HDFS, the "fs.default.name" cannot be used to get the namenode address. When such a setup co-exists with HDFS, with this change namenode can be identified using a separate configuration parameter "dfs.namenode.rpc-address".

      "dfs.namenode.rpc-address", when configured, overrides fs.default.name for identifying namenode RPC address.
      Show
      The namenode RPC address is currently identified from configuration "fs.default.name". In some setups where default FS is other than HDFS, the "fs.default.name" cannot be used to get the namenode address. When such a setup co-exists with HDFS, with this change namenode can be identified using a separate configuration parameter "dfs.namenode.rpc-address". "dfs.namenode.rpc-address", when configured, overrides fs.default.name for identifying namenode RPC address.

      Description

      When NameNode starts up, it tries to find out its address by looking at the fs.default.name configuration key instead of using its own keys. This breaks scenarios where we try to configure a Hadoop cluster that uses a different default file system than DFS, but still try to prop up namenode and datanode services as a secondary file system.

        Attachments

        1. HDFS-4320.branch-1.2.patch
          2 kB
          Mostafa Elhemali
        2. HDFS-4320.branch-1.3.patch
          3 kB
          Mostafa Elhemali
        3. HDFS-4320.patch
          0.9 kB
          Mostafa Elhemali
        4. HDFS-4320.trunk.2.patch
          2 kB
          Mostafa Elhemali
        5. HDFS-4320.trunk.patch
          1 kB
          Mostafa Elhemali
        6. HDFS-4320-trunk.3.patch
          0.7 kB
          Chuan Liu
        7. HDFS-4320-trunk.4.patch
          1 kB
          Chuan Liu

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              mostafae Mostafa Elhemali Assign to me
              Reporter:
              mostafae Mostafa Elhemali

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment