[
https://issues.apache.org/jira/browse/HADOOP-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1184:
-------------------------------------
Attachment: decommissionOneReplica3.patch
1. Incorporated Hairong's review comments. getPriority() now handles the case
when there is only one replica of the file and that node is being
decommissioned.
2. Enhanced the test case to have a test case for decommissioning a node that
has the only replica of a block.
3. Removed the checkDecommissioned() method from the ReplciationMonitor because
there is already a separate thread that checks whether the decommissioning was
complete.
4. Fixed a bug introduced in hadoop-988 that caused pendingTransfers to ignore
replicating blocks that have only one replica on a being-decommissioned node.
> 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
>
>
> 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.
