[ https://issues.apache.org/jira/browse/YARN-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513703#comment-15513703 ]
Tsuyoshi Ozawa commented on YARN-3139: -------------------------------------- [~leftnoteasy] [~jianhe] thanks for taking this issue. {quote} Summary: No regression in performance, didn't see deadlock happens. No significant performance improvement either, because existing scheduler allocation is still in single thread. {quote} If the performance doesn't change, could you clarify the reason to change this? Do you plan to make the scheduler allocation multi-threaded? > 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