hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-937) data node re-registration
Date Tue, 30 Jan 2007 22:44:33 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468808

Hadoop QA commented on HADOOP-937:

-1, because the patch command could not apply the latest attachment (http://issues.apache.org/jira/secure/attachment/12349950/register.patch</a>
applied and successfully tested against trunk revision r501249. </div>) as a patch to
trunk revision r501616. Please note that this message is automatically generated and may represent
a problem with the automation system and not the patch.

> data node re-registration
> -------------------------
>                 Key: HADOOP-937
>                 URL: https://issues.apache.org/jira/browse/HADOOP-937
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.10.1
>            Reporter: Hairong Kuang
>         Assigned To: Hairong Kuang
>             Fix For: 0.11.0
>         Attachments: register.patch
> A name node should ask a data node to re-register when
> 1) the name node restarts; or
> 2) the name node receives a heartbeat from an unregistered data node; or
> 3) the name node recieves a heartbeat from a data node whose heart beat is lost.
> In response to the re-registration request, the data node sends a register request followed
by a block report.

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

View raw message