hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Created: (HDFS-894) DatanodeID.ipcPort is not updated when existing node re-registers
Date Wed, 13 Jan 2010 03:17:54 GMT
DatanodeID.ipcPort is not updated when existing node re-registers

                 Key: HDFS-894
                 URL: https://issues.apache.org/jira/browse/HDFS-894
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 0.20.1, 0.21.0, 0.22.0
            Reporter: Todd Lipcon
            Priority: Blocker

In FSNamesystem.registerDatanode, it checks if a registering node is a reregistration of an
old one based on storage ID. If so, it simply updates the old one with the new registration
info. However, the new ipcPort is lost when this happens.

I produced manually this by setting up a DN with IPC port set to 0 (so it picks an ephemeral
port) and then restarting the DN. At this point, the NN's view of the ipcPort is stale, and
clients will not be able to achieve pipeline recovery.

This should be easy to fix and unit test, but not sure when I'll get to it, so anyone else
should feel free to grab it if they get to it first.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message