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 "Harsh J (JIRA)" <ji...@apache.org> on 2011/06/15 19:13:47 UTC

[jira] [Resolved] (HADOOP-3436) Useless synchronized in JobTracker

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

Harsh J resolved HADOOP-3436.
-----------------------------

    Resolution: Not A Problem

Does not appear to be a problem w.r.t. trunk. There is no such variable held (a collection is used instead, and that requires to hold JT lock and is synchronized (per comments)).

Resolving as "Not a problem" (anymore). Stale issue.

> Useless synchronized in JobTracker
> ----------------------------------
>
>                 Key: HADOOP-3436
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3436
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Brice Arnould
>            Assignee: Brice Arnould
>            Priority: Trivial
>
> In the original code, numTaskTrackers is fetch in a synchronized way, which is useless because anyway it might be change during the running of the algorithm.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira