Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6C39F183F6 for ; Wed, 16 Dec 2015 02:21:47 +0000 (UTC) Received: (qmail 75287 invoked by uid 500); 16 Dec 2015 02:21:47 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 75205 invoked by uid 500); 16 Dec 2015 02:21:47 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 74949 invoked by uid 99); 16 Dec 2015 02:21:47 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2015 02:21:47 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DFF682C1F86 for ; Wed, 16 Dec 2015 02:21:46 +0000 (UTC) Date: Wed, 16 Dec 2015 02:21:46 +0000 (UTC) From: "Alexey Tumanov (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (YARN-4198) CapacityScheduler locking / synchronization improvements MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Tumanov reassigned YARN-4198: ------------------------------------ Assignee: Alexey Tumanov > 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)