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 8DD9018847 for ; Thu, 19 Nov 2015 21:15:11 +0000 (UTC) Received: (qmail 98897 invoked by uid 500); 19 Nov 2015 21:15:11 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 98844 invoked by uid 500); 19 Nov 2015 21:15:11 -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 98809 invoked by uid 99); 19 Nov 2015 21:15:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2015 21:15:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 10AFB2C1F70 for ; Thu, 19 Nov 2015 21:15:11 +0000 (UTC) Date: Thu, 19 Nov 2015 21:15:11 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3769) Preemption occurring unnecessarily because preemption doesn't consider user limit 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-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014372#comment-15014372 ] Wangda Tan commented on YARN-3769: ---------------------------------- [~eepayne], thanks for update, could you check test failures of latest patch? It seems TestLeafQueue is still failing. > Preemption occurring unnecessarily because preemption doesn't consider user limit > --------------------------------------------------------------------------------- > > Key: YARN-3769 > URL: https://issues.apache.org/jira/browse/YARN-3769 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler > Affects Versions: 2.6.0, 2.7.0, 2.8.0 > Reporter: Eric Payne > Assignee: Eric Payne > Attachments: YARN-3769-branch-2.002.patch, YARN-3769-branch-2.7.002.patch, YARN-3769-branch-2.7.003.patch, YARN-3769-branch-2.7.005.patch, YARN-3769-branch-2.7.006.patch, YARN-3769-branch-2.7.007.patch, YARN-3769.001.branch-2.7.patch, YARN-3769.001.branch-2.8.patch, YARN-3769.003.patch, YARN-3769.004.patch, YARN-3769.005.patch > > > We are seeing the preemption monitor preempting containers from queue A and then seeing the capacity scheduler giving them immediately back to queue A. This happens quite often and causes a lot of churn. -- This message was sent by Atlassian JIRA (v6.3.4#6332)