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/05/03 03:10:15 UTC

[jira] Commented: (HADOOP-1184) Decommission fails if a block that needs replication has only one replica

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

Hairong Kuang commented on HADOOP-1184:
---------------------------------------

The new patch changed APIs for class UnderReplicatedBlocks to take an additional parameter decommissionedReplicas. This parameter is used only when numReplicas is equal to zero. But since the possibilty of numReplicas with a value of 0 is quite slim, I feel that making API changes for this special case is not neccessary.

> Decommission fails if a block that needs replication has only one replica
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-1184
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1184
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>         Attachments: decommissionOneReplica3.patch, decommissionOneReplica4.patch, decommissionOneReplica5.patch, decommissionOneReplica6.patch
>
>
> If the only replica of a block resides on a node being decommissioned, then the decommission command does not complete. The blocks do not get added to neededReplication because neededReplications.update() believes that the number of current replicas is zero.

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