[
https://issues.apache.org/jira/browse/HDFS-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222731#comment-14222731
]
Yi Liu edited comment on HDFS-7431 at 11/24/14 7:06 AM:
--------------------------------------------------------
So there are two cases for {{InvalidMagicNumberException}}:
*. failed handshake for encryption.
*. failed handshake for data transfer protection (only available after 2.6.0)
A simple way is change the log message to something like:
{quote}
Failed to read expected handshake from client at .... Perhaps the client is
running an older version of Hadoop which does not support the correct handshake.
{quote}
Or we can distinguish these two kinds of failure and give different log
messages.
What's your suggestion, [~cnauroth]?
was (Author: hitliuyi):
So there are two cases for {{InvalidMagicNumberException}}:
*. failed handshake for encryption.
*. failed handshake for data transfer protection (only available after 2.6.0)
A simply way is change the log message to something like:
{quote}
Failed to read expected handshake from client at .... Perhaps the client is
running an older version of Hadoop which does not support the correct handshake.
{quote}
Or we can distinguish these two kinds of failure and give different log
messages.
What's your suggestion, [~cnauroth]?
> 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
> Priority: Minor
>
> 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
(v6.3.4#6332)
