[jira] [Commented] (YARN-3091) [Umbrella] Improve locks of RM scheduler

["Wangda Tan (JIRA)" <ji...@apache.org>]

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

Wangda Tan commented on YARN-3091:
----------------------------------

Since some classes hierarchy are across module (like AbstractYarnScheduler inheriented by CS and fair). I suggest to make sub tasks class-family-wise. What I proposed for sub tasks are
# AbstractYarnScheduler - CapacityScheduler - FairScheduler
# SchedulerApplicationAttempt - FiCaSchedulerApp - FSAppAttempt
# AbstractCSQueue - ParentQueue - LeafQueue
# AppSchedulingInfo

Hope to get your thoughts on this, if you agree, I will go ahead and create sub-tickets.

Thanks,
Wangda

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