You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Harsh J (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/11 17:42:03 UTC

[jira] [Resolved] (MAPREDUCE-1109) ConcurrentModificationException in jobtracker.jsp

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

Harsh J resolved MAPREDUCE-1109.
--------------------------------

       Resolution: Not A Problem
    Fix Version/s: 1.0.0

This is no longer an issue in the current stable releases. The locking is properly taken care of, and the accessor methods to jobs map all hold lock before trying to work with it.

We've not seen this report come up in the past year as well.
                
> ConcurrentModificationException in jobtracker.jsp
> -------------------------------------------------
>
>                 Key: MAPREDUCE-1109
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1109
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.20.1
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>             Fix For: 1.0.0
>
>
> The jobtracker.jsp invoked methods tracker.runningJobs(), tracker.completedJobs() and tracker.failedJobs() but these methods are not synchronized and can cause ConcurrentModificationException if the JT is concurrently changing the contents of these datastructures.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira