[
https://issues.apache.org/jira/browse/YARN-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063346#comment-15063346
]
Hadoop QA commented on YARN-4198:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color}
| {color:red} YARN-4198 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12778405/YARN-4198-v1.patch |
| JIRA Issue | YARN-4198 |
| Powered by | Apache Yetus 0.2.0-SNAPSHOT http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/10031/console |
This message was automatically generated.
> 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
> Attachments: YARN-4198-v1.patch
>
>
> 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)
