hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7431) log message for InvalidMagicNumberException may be incorrect
Date Mon, 24 Nov 2014 10:46:13 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222871#comment-14222871

Hadoop QA commented on HDFS-7431:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision 555fa2d.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8818//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8818//console

This message is automatically generated.

> 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
>         Attachments: HDFS-7431.001.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