You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Xianyin Xin (JIRA)" <ji...@apache.org> on 2015/12/16 10:17:46 UTC

[jira] [Commented] (YARN-4198) CapacityScheduler locking / synchronization improvements

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

Xianyin Xin commented on YARN-4198:
-----------------------------------

Hi [~curino], does this improvement only considers the locking / synchronization that has relation with ReservationSystem? What's the relationship of this jira with YARN-3091 and the sub-jiras? 

> CapacityScheduler locking / synchronization improvements
> --------------------------------------------------------
>
>                 Key: YARN-4198
>                 URL: https://issues.apache.org/jira/browse/YARN-4198
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Carlo Curino
>            Assignee: Alexey Tumanov
>
> In the context of YARN-4193 (which stresses the RM/CS performance) we found several performance problems with  in the locking/synchronization of the CapacityScheduler, as well as inconsistencies that do not normally surface (incorrect locking-order of queues protected by CS locks etc). This JIRA proposes several refactoring that improve this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)