hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5185) Upate thread in FairScheduler runs too frequently
Date Fri, 06 Feb 2009 13:29:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671125#action_12671125

Vinod K V commented on HADOOP-5185:

As Hemanth commented offline, update thread doesn't lock the JT as such. But it does lock
'taskTrackers' HashMap via getTotalSlots method. This still can get problematic and needs
to  be fixed.

> Upate thread in FairScheduler runs too frequently
> -------------------------------------------------
>                 Key: HADOOP-5185
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5185
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/fair-share
>            Reporter: Vinod K V
> 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