hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yi Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7431) log message for InvalidMagicNumberException may be incorrect
Date Tue, 16 Dec 2014 08:24:13 GMT

     [ https://issues.apache.org/jira/browse/HDFS-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Yi Liu updated HDFS-7431:
    Attachment: HDFS-7431.003.patch

Hi Chris, sorry for the late update, I was not available last week.
Please review the new patch.

> log message for InvalidMagicNumberException may be incorrect
> ------------------------------------------------------------
>                 Key: HDFS-7431
>                 URL: https://issues.apache.org/jira/browse/HDFS-7431
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: security
>            Reporter: Yi Liu
>            Assignee: Yi Liu
>         Attachments: HDFS-7431.001.patch, HDFS-7431.002.patch, HDFS-7431.003.patch
> 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:
> {quote}
> Failed to read expected encryption handshake from client at .... Perhaps the client is
running an older version of Hadoop which does not support encryption
> {quote}
> 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.

This message was sent by Atlassian JIRA

View raw message