hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matei Zaharia (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (MAPREDUCE-540) Upate thread in FairScheduler runs too frequently
Date Tue, 30 Jun 2009 20:50:47 GMT

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

Matei Zaharia resolved MAPREDUCE-540.

    Resolution: Fixed
      Assignee: Matei Zaharia

Alright, closing the JIRA because it is resolved in MAPREDUCE-551.

> Upate thread in FairScheduler runs too frequently
> -------------------------------------------------
>                 Key: MAPREDUCE-540
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-540
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Vinod K V
>            Assignee: Matei Zaharia
> The UpdateThread in FairScheduler runs every 500ms (hardcoded). This proves to be very
costly when running large clusters. UpdateThread tries to acquire lock on JT object every
that often and so seriously affects HeartBeat processing besides everything else. The update
interval should be a function of the cluster size. Or in the minimum it should be configurable
and by default should be set to a reasonably high default value.

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

View raw message