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/04/14 01:24: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_12488816 ]
Hairong Kuang commented on HADOOP-1184:
---------------------------------------
For change 4:
The parameter to UnderReplicatedBlocks.getPriority() is the number of nondecommisioning replicas. So I do not think by simply changing the priority of blocks with 0 nondecomissioning replicas to be 0 solves the problem. If a block has zero replicas, it needs to be deleted from the underReplicatedBlocks queue by having an invalid priority level. Only the block with zero nondecomissioning replicas needs to have 0 priority.
> 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: decommissionOneReplica2.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.