[
https://issues.apache.org/jira/browse/HADOOP-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473766
]
Hadoop QA commented on HADOOP-947:
----------------------------------
+1, because
http://issues.apache.org/jira/secure/attachment/12351377/isReplicationInProgress2.patch
applied and successfully tested against trunk revision r508345.
> isReplicationInProgress() is very heavyweight
> ---------------------------------------------
>
> Key: HADOOP-947
> URL: https://issues.apache.org/jira/browse/HADOOP-947
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assigned To: dhruba borthakur
> Attachments: isReplicationInProgress2.patch
>
>
> Suppose a decommission is in progress. The namenode receives a heartbeat from
> the being-decommissioned node and then invokes isReplicationInProgress() to
> determine if the decommissioned is complete. This method is very heavyweight
> and chews up plenty of CPU.
> One option to fix this issue is to keep a counter to indicate how many blocks
> are pending replication. This could also help in showing a
> progress-status-indicator to display how far the decommissioning process is
> complete.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
