You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2012/06/05 09:27:23 UTC
[jira] [Commented] (MAPREDUCE-2224) Synchronization bugs in
JvmManager
[ https://issues.apache.org/jira/browse/MAPREDUCE-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289208#comment-13289208 ]
Konstantin Shvachko commented on MAPREDUCE-2224:
------------------------------------------------
This is already committed to 0.22 and should go into a separate jira.
Created MAPREDUCE-4314 to commit the patch.
> Synchronization bugs in JvmManager
> ----------------------------------
>
> Key: MAPREDUCE-2224
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2224
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Fix For: 0.22.0
>
> Attachments: mapreduce-2224-cdh3.txt, mapreduce-2224.txt, mapreduce-2224.txt, mapreduce-2224.txt, mapreduce-2224.txt, mr-2224-0.22.patch, mr-2224-0.22.patch
>
>
> JvmManager.JvmManagerForType has several HashMap members that are inconsistently synchronized. I've seen sporadic NPEs in the 0.20 version of this code which has similar bugs.
--
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