hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1126) Optimize CPU usage when cluster restarts
Date Tue, 02 Feb 2010 06:18:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828478#action_12828478
] 

Hudson commented on HADOOP-1126:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #225 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/225/])
    

> Optimize CPU usage when cluster restarts
> ----------------------------------------
>
>                 Key: HADOOP-1126
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1126
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: dhruba borthakur
>            Assignee: Hairong Kuang
>             Fix For: 0.12.1
>
>         Attachments: neededReplicationRemove.patch
>
>
> When the namenode restarts, all datanodes report their blocks to the namenode. The namenode
inserts these blocks into neededReplication(). When safemode exists, pendingTransfers removes
them from neededReplication. This is non-optimal because pendingTransfer consumes plenty of
CPU just after exiting safe-mode.
> The problem is that neededReplications.remove(block) does not remove a block if oldExpectedReplicas
is exactly equal to oldReplicas.

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


Mime
View raw message