hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-894) DatanodeID.ipcPort is not updated when existing node re-registers
Date Tue, 09 Feb 2010 22:55:28 GMT

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

dhruba borthakur commented on HDFS-894:

The code looks good. But since this is not a regression (and datanodes typically re-register
with the same ipcPort) can we put this patch only in trunk?

> 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
>         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.

View raw message