hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-3899) Locking not correct in org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService.allocate(AllocateRequest request)
Date Wed, 22 Feb 2012 23:19:49 GMT
Locking not correct in org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService.allocate(AllocateRequest
request)
-------------------------------------------------------------------------------------------------------------------------------

                 Key: MAPREDUCE-3899
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3899
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mrv2, resourcemanager
    Affects Versions: 0.23.0
            Reporter: Bikas Saha
            Assignee: Bikas Saha
             Fix For: 0.23.0


Looks like the lock taken in this is broken. It takes a lock on lastResponse object and then
puts a new lastResponse object into the map. At this point a new thread entering this function
will get a new lastResponse object and will be able to take its lock and enter the critical
section. Presumably we want to limit one response per app attempt. So the lock could be taken
on the ApplicationAttemptId key of the response map object.

--
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

        

Mime
View raw message