hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3224) Bug in check for DN re-registration with different storage ID
Date Mon, 08 Oct 2012 16:36:03 GMT

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

Jason Lowe updated HDFS-3224:

    Attachment: HDFS-3224.patch

Updated patch with refactored interface in Host2NodesMap and a test case.

I thought it would be good to have the old getDatanodeByName interface explicitly take the
IP address and xfer port arguments.  It's clearer what is expected, and the old interface
would silently fail if the :port portion was missing from the address string.
> Bug in check for DN re-registration with different storage ID
> -------------------------------------------------------------
>                 Key: HDFS-3224
>                 URL: https://issues.apache.org/jira/browse/HDFS-3224
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Eli Collins
>            Assignee: Jason Lowe
>            Priority: Minor
>         Attachments: HDFS-3224.patch, HDFS-3224.patch
> DatanodeManager#registerDatanode checks the host to node map using an IP:port key, however
the map is keyed on IP, so this check will always fail. It's performing the check to determine
if a DN with the same IP and storage ID has already registered, and if so to remove this DN
from the map and indicate that eg it's no longer hosting these blocks. This bug has been here

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message