You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2007/01/25 21:56:49 UTC

[jira] Created: (HADOOP-937) data node re-registration

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
             Fix For: 0.11.0


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.


[jira] Commented: (HADOOP-937) data node re-registration

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468167 ] 

Hadoop QA commented on HADOOP-937:
----------------------------------

+1, because http://issues.apache.org/jira/secure/attachment/12349749/register.patch applied and successfully tested against trunk revision r500415.

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


[jira] Assigned: (HADOOP-937) data node re-registration

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang reassigned HADOOP-937:
------------------------------------

    Assignee: Hairong Kuang

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


[jira] Updated: (HADOOP-937) data node re-registration

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HADOOP-937:
---------------------------------

    Status: In Progress  (was: Patch Available)

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


[jira] Commented: (HADOOP-937) data node re-registration

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Updated: (HADOOP-937) data node re-registration

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HADOOP-937:
---------------------------------

    Status: Patch Available  (was: In Progress)

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


[jira] Updated: (HADOOP-937) data node re-registration

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting updated HADOOP-937:
--------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this.  Thanks, Hairong!

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


[jira] Commented: (HADOOP-937) data node re-registration

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468378 ] 

Doug Cutting commented on HADOOP-937:
-------------------------------------

Do you think this change to the protocol is entirely back-compatible, or should we also increment the version number of DataNode protocol?

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


[jira] Updated: (HADOOP-937) data node re-registration

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HADOOP-937:
---------------------------------

    Status: Patch Available  (was: Open)

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


[jira] Updated: (HADOOP-937) data node re-registration

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HADOOP-937:
---------------------------------

    Attachment: register.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.


[jira] Commented: (HADOOP-937) data node re-registration

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468801 ] 

Hadoop QA commented on HADOOP-937:
----------------------------------

+1, because http://issues.apache.org/jira/secure/attachment/12349950/register.patch applied and successfully tested against trunk revision r501249.

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


[jira] Updated: (HADOOP-937) data node re-registration

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HADOOP-937:
---------------------------------

    Attachment:     (was: register.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
>
>
> 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.


[jira] Updated: (HADOOP-937) data node re-registration

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HADOOP-937:
---------------------------------

    Attachment: register.patch

Although the patch does not change the format of the datanode protocol, it changes its sematics. So I bumped up its version number.

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