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

log message for InvalidMagicNumberException may be incorrect

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.7.0
    • Component/s: security
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      For security mode, HDFS now supports that Datanodes don't require root or jsvc if dfs.data.transfer.protection is configured.

      Log message for InvalidMagicNumberException, we miss one case:
      when the datanodes run on unprivileged port and dfs.data.transfer.protection is configured to authentication but dfs.encrypt.data.transfer is not configured. SASL handshake is required and a low version dfs client is used, then InvalidMagicNumberException is thrown and we write log:

      Failed to read expected encryption handshake from client at .... Perhaps the client is running an older version of Hadoop which does not support encryption

      Recently I run HDFS built on trunk and security is enabled, but the client is 2.5.1 version. Then I got the above log message, but actually I have not configured encryption.

        Attachments

        1. HDFS-7431.001.patch
          2 kB
          Yi Liu
        2. HDFS-7431.002.patch
          8 kB
          Yi Liu
        3. HDFS-7431.003.patch
          7 kB
          Yi Liu

          Issue Links

            Activity

              People

              • Assignee:
                hitliuyi Yi Liu
                Reporter:
                hitliuyi Yi Liu
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: