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 "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2015/03/17 20:26:39 UTC

[jira] [Resolved] (YARN-3355) findbugs warning:Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.allocConf

     [ https://issues.apache.org/jira/browse/YARN-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla resolved YARN-3355.
------------------------------------
    Resolution: Duplicate

These warnings are due to YARN-3181. I just reopened it to revert that commit. Let us follow this up there? I am open to someone taking it over. 

> findbugs warning:Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.allocConf
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3355
>                 URL: https://issues.apache.org/jira/browse/YARN-3355
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>              Labels: findbugs
>
> findbugs warning:Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.allocConf
> The findbugs warning found out two Unsynchronized access:
> 1. FairScheduler.getPlanQueues.
> It looks like we should add lock at FairScheduler.getPlanQueues.
> Because getPlanQueues will be called by AbstractReservationSystem.reinitialize.
> 2. FairScheduler.getAllocationConfiguration, which looks like ok without lock.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)