[
https://issues.apache.org/jira/browse/YARN-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513822#comment-15513822
]
Wangda Tan commented on YARN-3139:
----------------------------------
[~ozawa],
Yeah we plan to add multi-threading scheduling implementation. This change is
first step of the YARN-5139. You can check [design
doc|https://issues.apache.org/jira/secure/attachment/12825344/YARN-5139-Global-Schedulingd-esign-and-implementation-notes-v2.pdf],
and [implementation
notes|https://github.com/leftnoteasy/hadoop/blob/global-scheduling-3/global-scheduling-explaination.md]
for details.
To avoid disruptive changes, we just want to simply convert synchronized lock
to R/W lock for this patch, will do more fine-grained improvements in separate
patches.
> Improve locks in AbstractYarnScheduler/CapacityScheduler/FairScheduler
> ----------------------------------------------------------------------
>
> Key: YARN-3139
> URL: https://issues.apache.org/jira/browse/YARN-3139
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager, scheduler
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-3139.0.patch, YARN-3139.1.patch, YARN-3139.2.patch
>
>
> Enhance locks in AbstractYarnScheduler/CapacityScheduler/FairScheduler, as
> mentioned in YARN-3091, a possible solution is using read/write lock. Other
> fine-graind locks for specific purposes / bugs should be addressed in
> separated tickets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
