hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5145) Balancer sometimes runs out of memory after days or weeks running
Date Fri, 13 Mar 2009 15:05:57 GMT

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

Hudson commented on HADOOP-5145:
--------------------------------

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

> Balancer sometimes runs out of memory after days or weeks running
> -----------------------------------------------------------------
>
>                 Key: HADOOP-5145
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5145
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.20.0
>
>         Attachments: balancerOME.patch, balancerOME1.patch
>
>
> The culprit is a HashMap called MovedBlocks. By design this map does not get cleaned
up between iterations. This is because the deletion of source replicas is done by NN. When
next iteration starts, source replicas may not have been deleted, Balancer does not want to
schedule them to move again. To prevent running out of memory, Balancer should expire/clean
the movedBlocks from some iterations back.

-- 
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