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 9452D18202 for ; Fri, 8 Jan 2016 14:56:41 +0000 (UTC) Received: (qmail 12701 invoked by uid 500); 8 Jan 2016 14:56:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 12366 invoked by uid 500); 8 Jan 2016 14:56:40 -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 12250 invoked by uid 99); 8 Jan 2016 14:56:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jan 2016 14:56:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D16F02C0451 for ; Fri, 8 Jan 2016 14:56:39 +0000 (UTC) Date: Fri, 8 Jan 2016 14:56:39 +0000 (UTC) From: "Karam Singh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-4565) When sizeBasedWeight enabled for FairOrderingPolicy in CapacityScheduler, Sometimes lead to situation where all queue resources consumed by AMs only MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Karam Singh created YARN-4565: --------------------------------- Summary: When sizeBasedWeight enabled for FairOrderingPolicy in CapacityScheduler, Sometimes lead to situation where all queue resources consumed by AMs only Key: YARN-4565 URL: https://issues.apache.org/jira/browse/YARN-4565 Project: Hadoop YARN Issue Type: Bug Components: capacity scheduler, capacityscheduler Affects Versions: 2.7.1, 2.8.0 Reporter: Karam Singh When sizeBasedWeight enabled for FairOrderingPolicy in CapacityScheduler, Sometimes lead to situation where all queue resources consumed by AMs only, So from users perpective it appears that all application in queue are stuck, whole queue capacity is comsumed by AMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)