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

webhdfs requests can be routed incorrectly in federated cluster

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.1, 3.0.3
    • Component/s: webhdfs
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      In the following HA+Federated setup with two nameservices ns1 and ns2:

      1. ns1 -> namenodes nn1, nn2
      2. ns2 -> namenodes nn3, nn4
      3. fs.defaultFS is hdfs://ns1.

      A webhdfs request issued to nn3/nn4 will be routed to ns1. This is because setClientNamenodeAddress initializes NameNode#clientNamenodeAddress using fs.defaultFS before the config is overriden.

        Attachments

        1. HDFS-13433.01.patch
          12 kB
          Arpit Agarwal
        2. HDFS-13433.02.patch
          12 kB
          Arpit Agarwal
        3. HDFS-13433.03.patch
          12 kB
          Arpit Agarwal
        4. HDFS-13433.04.patch
          12 kB
          Arpit Agarwal

          Issue Links

            Activity

              People

              • Assignee:
                arpitagarwal Arpit Agarwal
                Reporter:
                arpitagarwal Arpit Agarwal
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: