You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/10/01 20:07:50 UTC

[jira] Updated: (HADOOP-1946) du should be not called on every heartbeat

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

dhruba borthakur updated HADOOP-1946:
-------------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this. Thanks Hairong!

> du should be not called on every heartbeat
> ------------------------------------------
>
>                 Key: HADOOP-1946
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1946
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.15.0
>            Reporter: Konstantin Shvachko
>            Assignee: Hairong Kuang
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: du.patch, du.patch, du2.patch
>
>
> Data-nodes run very slow. The reason is that du is executed on each and every heartbeat.
> Looks like the condition in DU.getUsed(), which triggers the refresh of cached values, should be reversed.

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