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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2007/04/06 21:05:32 UTC

[jira] Commented: (HADOOP-1218) In TaskTracker the access to RunningJob object is not synchronized in one place

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

Hadoop QA commented on HADOOP-1218:
-----------------------------------

-1, because 1 attempts failed to build and test the latest attachment http://issues.apache.org/jira/secure/attachment/12355101/1218.patch against trunk revision http://svn.apache.org/repos/asf/lucene/hadoop/trunk/526215. Please note that this message is automatically generated and may represent a problem with the automation system and not the patch. Results are at http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch

> In TaskTracker the access to RunningJob object is not synchronized in one place
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-1218
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1218
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Devaraj Das
>         Assigned To: Devaraj Das
>             Fix For: 0.13.0
>
>         Attachments: 1218.patch
>
>
> In the method addTaskToJob, the access to RunningJob is not synchronized (leading to potential race conditions).

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