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 084CE17CB0 for ; Tue, 14 Apr 2015 22:38:01 +0000 (UTC) Received: (qmail 10819 invoked by uid 500); 14 Apr 2015 22:38:00 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 10760 invoked by uid 500); 14 Apr 2015 22:38:00 -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 10650 invoked by uid 99); 14 Apr 2015 22:38:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Apr 2015 22:38:00 +0000 Date: Tue, 14 Apr 2015 22:38:00 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3487) CapacityScheduler.getQueueInfo grabs scheduler lock unnecessarily 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-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495045#comment-14495045 ] Wangda Tan commented on YARN-3487: ---------------------------------- Patch LGTM +1. > CapacityScheduler.getQueueInfo grabs scheduler lock unnecessarily > ----------------------------------------------------------------- > > Key: YARN-3487 > URL: https://issues.apache.org/jira/browse/YARN-3487 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler > Affects Versions: 2.6.0 > Reporter: Jason Lowe > Assignee: Jason Lowe > Priority: Critical > Attachments: YARN-3487.001.patch > > > Recently saw a significant slowdown of applications on a large cluster, and we noticed there were a large number of blocked threads on the RM. Most of the blocked threads were waiting for the CapacityScheduler lock while calling getQueueInfo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)