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 0F2C718F78 for ; Tue, 8 Mar 2016 23:01:41 +0000 (UTC) Received: (qmail 11838 invoked by uid 500); 8 Mar 2016 23:01:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 11783 invoked by uid 500); 8 Mar 2016 23:01: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 11756 invoked by uid 99); 8 Mar 2016 23:01:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2016 23:01:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AD1582C044E for ; Tue, 8 Mar 2016 23:01:40 +0000 (UTC) Date: Tue, 8 Mar 2016 23:01:40 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-4779) Fix AM container allocation logic in SLS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Wangda Tan created YARN-4779: -------------------------------- Summary: Fix AM container allocation logic in SLS Key: YARN-4779 URL: https://issues.apache.org/jira/browse/YARN-4779 Project: Hadoop YARN Issue Type: Bug Reporter: Wangda Tan Assignee: Wangda Tan Currently, SLS uses unmanaged AM for simulated map-reduce applications. And first allocated container for each app is considered to be the master container. This could be problematic when preemption happens. CapacityScheduler preempt AM container at lowest priority, but the simulated AM container isn't recognized by scheduler -- it is a normal container from scheduler's perspective. This JIRA tries to fix this logic: do the real AM allocation instead of using unmanaged AM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)