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

Rohith commented on YARN-3091:
------------------------------

bq. fixing improperly synchronized data accesses in RM scheduler (correctness)
currently findbug exclude xml mask these warnings like IS2_INCONSISTENT_SYNC. I 
believe these exclude lists are reviewed and now assumptions like a class 
expected to be thread-safe. Recently had discussion on this in community 
[Discussion 
thread|http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201412.mbox/%3CCALwhT97BqK_zjQ=MCO_c=Y=7r9ewLN2Ab_qm=vqekvxgzrq...@mail.gmail.com%3E]

For identifying 1st level of problems, I think enabling these findbug type 
would help in better way.

> [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)

Reply via email to