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 F168517623 for ; Tue, 16 Feb 2016 03:43:18 +0000 (UTC) Received: (qmail 91756 invoked by uid 500); 16 Feb 2016 03:43:18 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 91673 invoked by uid 500); 16 Feb 2016 03:43:18 -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 91316 invoked by uid 99); 16 Feb 2016 03:43:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Feb 2016 03:43:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2CFE72C1F64 for ; Tue, 16 Feb 2016 03:43:18 +0000 (UTC) Date: Tue, 16 Feb 2016 03:43:18 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (YARN-2887) AM policies for choosing type of containers 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-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh resolved YARN-2887. ------------------------------- Resolution: Not A Problem This is more an AM / application specific change and should not be part of core YARN > AM policies for choosing type of containers > ------------------------------------------- > > Key: YARN-2887 > URL: https://issues.apache.org/jira/browse/YARN-2887 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager > Reporter: Konstantinos Karanasos > > Each AM can employ policies that determine what type of container (guaranteed-start or queueable) should be requested for each task. > An example policy may be to use only guaranteed-start or only queueable containers, or to randomly pick a percentage of the requests to be queueable, or to choose the container type based on the characteristics of the tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)