hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1296) schedulerAllocateTimer is accessed without holding samplerLock in ResourceSchedulerWrapper
Date Fri, 11 Oct 2013 03:34:42 GMT

    [ https://issues.apache.org/jira/browse/YARN-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792303#comment-13792303
] 

Ted Yu commented on YARN-1296:
------------------------------

I found these two fair-scheduler-allocation.xml :

./hadoop-tools/hadoop-sls/src/main/sample-conf/fair-scheduler-allocation.xml
./hadoop-tools/hadoop-sls/src/test/resources/fair-scheduler-allocation.xml

But they seem to have '<allocations>' as top-level element.

> 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
>            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.1#6144)

Mime
View raw message