[
https://issues.apache.org/jira/browse/HDFS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853673#action_12853673
]
Hudson commented on HDFS-894:
-----------------------------
Integrated in Hdfs-Patch-h2.grid.sp2.yahoo.net #146 (See
[http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/146/])
> 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
> Components: name-node
> Affects Versions: 0.20.1, 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.22.0
>
> Attachments: hdfs-894.txt
>
>
> 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.
