[
https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709304#comment-13709304
]
Omkar Vinit Joshi commented on YARN-744:
----------------------------------------
bq. We should not be locking on the app attempt id.
I am not locking on appAttemptId... or AppAttemptImpl...didn't understand your
question.
bq. Why do we need a wrapper?
We don't have any explicit lock for an application attempt...I am creating a
wrapped object to avoid maintaining per application attempt lock. Thereby
across application attempt response we can lock on specific attempt.
I think this is important as we may loose container than what were requested...
> Race condition in ApplicationMasterService.allocate .. It might process same
> allocate request twice resulting in additional containers getting allocated.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-744
> URL: https://issues.apache.org/jira/browse/YARN-744
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Bikas Saha
> Assignee: Omkar Vinit Joshi
> Priority: Minor
> Attachments: MAPREDUCE-3899-branch-0.23.patch,
> YARN-744-20130711.1.patch, YARN-744-20130715.1.patch, YARN-744.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
