hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1126) Optimize CPU usage when cluster restarts
Date Sat, 17 Mar 2007 00:07:10 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hairong Kuang updated HADOOP-1126:
----------------------------------

        Fix Version/s: 0.12.1
    Affects Version/s: 0.12.0
               Status: Patch Available  (was: Open)

> Optimize CPU usage when cluster restarts
> ----------------------------------------
>
>                 Key: HADOOP-1126
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1126
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.12.0
>            Reporter: dhruba borthakur
>         Assigned To: 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