Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <8337410.1191023690717.JavaMail.jira@brutus>
Date: Fri, 28 Sep 2007 16:54:50 -0700 (PDT)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1946) du should be not called on every
 heartbeat
In-Reply-To: <6780154.1190761190959.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Shvachko commented on HADOOP-1946:
---------------------------------------------

+1

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