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

dfs.namenode.send.qop.enabled should not apply to primary NN port

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.10.1, 3.3.1
    • 3.3.0, 3.1.4, 3.2.2, 2.10.1
    • None
    • None

    Description

      In HDFS-13617, NameNode can be configured to wrap its established QOP into block access token as an encrypted message. Later on DataNode will use this message to create SASL connection. But this new behavior should only apply to new auxiliary NameNode ports, not the primary port (the one configured in fs.defaultFS), as it may cause conflicting behavior with existing other SASL related configuration (e.g. dfs.data.transfer.protection). Since this configure is introduced for to auxiliary ports only, we should restrict this new behavior to not apply to primary port.

      Attachments

        1. HDFS-15148.001.patch
          12 kB
          Chen Liang
        2. HDFS-15148.002.patch
          16 kB
          Chen Liang
        3. HDFS-15148.003.patch
          18 kB
          Chen Liang
        4. HDFS-15148.004.patch
          18 kB
          Chen Liang

        Activity

          People

            vagarychen Chen Liang
            vagarychen Chen Liang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: