[
https://issues.apache.org/jira/browse/YARN-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288755#comment-14288755
]
Li Lu commented on YARN-3091:
-----------------------------
I agree we should review the exclude list for potential synchronization
problems. However note that findbugs uses static analysis to analyze Java
source code, which may introduce both false positives and false negatives when
detecting concurrency related bugs. In long term we may want to consider other
tools to help detect improper synchronization (although a perfect solution
would be hard). For the short term, I think [~leftnoteasy] raised a very valid
point (this JIRA) and let's the the problems solved.
> [Umbrella] Improve locks of RM scheduler
> ----------------------------------------
>
> Key: YARN-3091
> URL: https://issues.apache.org/jira/browse/YARN-3091
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler, fairscheduler, resourcemanager,
> scheduler
> Reporter: Wangda Tan
>
> In existing YARN RM scheduler, there're some issues of using locks. For
> example:
> - Many unnecessary synchronized locks, we have seen several cases recently
> that too frequent access of scheduler makes scheduler hang. Which could be
> addressed by using read/write lock. Components include scheduler, CS queues,
> apps
> - Some fields not properly locked (Like clusterResource)
> We can address them together in this ticket.
> (More details see comments below)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
