You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2015/03/29 17:23:53 UTC
[jira] [Resolved] (YARN-1296) schedulerAllocateTimer is accessed
without holding samplerLock in ResourceSchedulerWrapper
[ https://issues.apache.org/jira/browse/YARN-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu resolved YARN-1296.
--------------------------
Resolution: Later
> schedulerAllocateTimer is accessed without holding samplerLock in ResourceSchedulerWrapper
> ------------------------------------------------------------------------------------------
>
> Key: YARN-1296
> URL: https://issues.apache.org/jira/browse/YARN-1296
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Attachments: yarn-1296-v1.patch
>
>
> Here is related code:
> {code}
> public Allocation allocate(ApplicationAttemptId attemptId,
> List<ResourceRequest> resourceRequests,
> List<ContainerId> containerIds,
> List<String> strings, List<String> strings2) {
> if (metricsON) {
> final Timer.Context context = schedulerAllocateTimer.time();
> {code}
> samplerLock should be used to guard the access.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)