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 "Nigel Daley (JIRA)" <ji...@apache.org> on 2007/03/07 20:35:24 UTC
[jira] Created: (HADOOP-1083) Replication not occuring after
cluster restart when datanodes missing
Replication not occuring after cluster restart when datanodes missing
---------------------------------------------------------------------
Key: HADOOP-1083
URL: https://issues.apache.org/jira/browse/HADOOP-1083
Project: Hadoop
Issue Type: Bug
Components: dfs
Affects Versions: 0.11.2
Reporter: Nigel Daley
Priority: Blocker
Fix For: 0.12.1
When a cluster is restarted, but one or more datanodes do not start, the blocks on those missing datanodes are not replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1083) Replication not occuring after
cluster restart when datanodes missing
Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hairong Kuang updated HADOOP-1083:
----------------------------------
Status: Patch Available (was: Open)
> Replication not occuring after cluster restart when datanodes missing
> ---------------------------------------------------------------------
>
> Key: HADOOP-1083
> URL: https://issues.apache.org/jira/browse/HADOOP-1083
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.11.2
> Reporter: Nigel Daley
> Assigned To: Hairong Kuang
> Priority: Blocker
> Fix For: 0.12.1
>
> Attachments: replicateBlock.patch
>
>
> When a cluster is restarted, but one or more datanodes do not start, the blocks on those missing datanodes are not replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1083) Replication not occuring after
cluster restart when datanodes missing
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1083:
---------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Hairong!
> Replication not occuring after cluster restart when datanodes missing
> ---------------------------------------------------------------------
>
> Key: HADOOP-1083
> URL: https://issues.apache.org/jira/browse/HADOOP-1083
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.11.2
> Reporter: Nigel Daley
> Assigned To: Hairong Kuang
> Priority: Blocker
> Fix For: 0.12.1
>
> Attachments: replicateBlock.patch
>
>
> When a cluster is restarted, but one or more datanodes do not start, the blocks on those missing datanodes are not replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1083) Replication not occuring after
cluster restart when datanodes missing
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478947 ]
dhruba borthakur commented on HADOOP-1083:
------------------------------------------
+1. Code reviewed. Looks good.
> Replication not occuring after cluster restart when datanodes missing
> ---------------------------------------------------------------------
>
> Key: HADOOP-1083
> URL: https://issues.apache.org/jira/browse/HADOOP-1083
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.11.2
> Reporter: Nigel Daley
> Assigned To: Hairong Kuang
> Priority: Blocker
> Fix For: 0.12.1
>
> Attachments: replicateBlock.patch
>
>
> When a cluster is restarted, but one or more datanodes do not start, the blocks on those missing datanodes are not replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-1083) Replication not occuring after
cluster restart when datanodes missing
Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hairong Kuang reassigned HADOOP-1083:
-------------------------------------
Assignee: Hairong Kuang
> Replication not occuring after cluster restart when datanodes missing
> ---------------------------------------------------------------------
>
> Key: HADOOP-1083
> URL: https://issues.apache.org/jira/browse/HADOOP-1083
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.11.2
> Reporter: Nigel Daley
> Assigned To: Hairong Kuang
> Priority: Blocker
> Fix For: 0.12.1
>
>
> When a cluster is restarted, but one or more datanodes do not start, the blocks on those missing datanodes are not replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1083) Replication not occuring after
cluster restart when datanodes missing
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478963 ]
Nigel Daley commented on HADOOP-1083:
-------------------------------------
+1. I have manually tested this patch. I now see replications taking place right away for missing blocks. If I bring the missing node back on line, replications stop and over replicated blocks are deleted. Very cool! It would be nice to have a unit test for this case.
> Replication not occuring after cluster restart when datanodes missing
> ---------------------------------------------------------------------
>
> Key: HADOOP-1083
> URL: https://issues.apache.org/jira/browse/HADOOP-1083
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.11.2
> Reporter: Nigel Daley
> Assigned To: Hairong Kuang
> Priority: Blocker
> Fix For: 0.12.1
>
> Attachments: replicateBlock.patch
>
>
> When a cluster is restarted, but one or more datanodes do not start, the blocks on those missing datanodes are not replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1083) Replication not occuring after
cluster restart when datanodes missing
Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hairong Kuang updated HADOOP-1083:
----------------------------------
Attachment: replicateBlock.patch
This patch allows under replicated blocks to be added to neededReplication when data nodes get started
> Replication not occuring after cluster restart when datanodes missing
> ---------------------------------------------------------------------
>
> Key: HADOOP-1083
> URL: https://issues.apache.org/jira/browse/HADOOP-1083
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.11.2
> Reporter: Nigel Daley
> Assigned To: Hairong Kuang
> Priority: Blocker
> Fix For: 0.12.1
>
> Attachments: replicateBlock.patch
>
>
> When a cluster is restarted, but one or more datanodes do not start, the blocks on those missing datanodes are not replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.