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-1946) du should be not called on every heartbeat
Date Fri, 28 Sep 2007 19:25:50 GMT

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

Hairong Kuang updated HADOOP-1946:

    Attachment: du.patch

The patch includes:
1. a unit test to make sure that du does not run every time getUsed is called.
2. restructure DU, DF, and Command so that the code that checking if a shell command needs
to be run is factored into the parent class Command.

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

View raw message