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

Jason Lowe commented on HDFS-3688:
----------------------------------

Patch failed on trunk since it's only for 23.  Manually ran test-patch for this 
on branch-0.23, here's the output:

{noformat}
-1 overall.  

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version ) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed these unit tests:
                  org.apache.hadoop.hdfs.TestDatanodeBlockScanner

    +1 contrib tests.  The patch passed contrib unit tests.
{noformat}

The test failure appears to be unrelated, and when I ran the test again 
manually it passed.  I believe this test is known to have some races in it, see 
HDFS-2881.
                
> Namenode loses datanode hostname if datanode re-registers
> ---------------------------------------------------------
>
>                 Key: HDFS-3688
>                 URL: https://issues.apache.org/jira/browse/HDFS-3688
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>         Attachments: HDFS-3688.patch
>
>
> If a datanode ever re-registers with the namenode (e.g.: namenode restart, 
> temporary network cut, etc.) then the datanode ends up registering with an IP 
> address as the datanode name rather than the hostname.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to