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 39D2D19F42 for ; Wed, 20 Apr 2016 16:01:27 +0000 (UTC) Received: (qmail 91357 invoked by uid 500); 20 Apr 2016 16:01:26 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 91251 invoked by uid 500); 20 Apr 2016 16:01:26 -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 91099 invoked by uid 99); 20 Apr 2016 16:01:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2016 16:01:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id ACBFF2C1F6F for ; Wed, 20 Apr 2016 16:01:25 +0000 (UTC) Date: Wed, 20 Apr 2016 16:01:25 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-2883) Queuing of container requests in the NM 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-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250145#comment-15250145 ] Karthik Kambatla commented on YARN-2883: ---------------------------------------- Latest patch looks good to me. +1 The tests introduced seem to add long sleeps, or bump up existing sleeps. We should definitely clean this up, similar to YARN-4807. [~asuresh], [~kkaranasos] - can we file a follow-up JIRA along the same lines? > Queuing of container requests in the NM > --------------------------------------- > > Key: YARN-2883 > URL: https://issues.apache.org/jira/browse/YARN-2883 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager > Reporter: Konstantinos Karanasos > Assignee: Konstantinos Karanasos > Attachments: YARN-2883-trunk.004.patch, YARN-2883-trunk.005.patch, YARN-2883-trunk.006.patch, YARN-2883-trunk.007.patch, YARN-2883-trunk.008.patch, YARN-2883-trunk.009.patch, YARN-2883-trunk.010.patch, YARN-2883-trunk.011.patch, YARN-2883-trunk.012.patch, YARN-2883-trunk.013.patch, YARN-2883-yarn-2877.001.patch, YARN-2883-yarn-2877.002.patch, YARN-2883-yarn-2877.003.patch, YARN-2883-yarn-2877.004.patch, YARN-2883.013.patch, YARN-2883.014.patch, YARN-2883.015.patch > > > We propose to add a queue in each NM, where queueable container requests can be held. > Based on the available resources in the node and the containers in the queue, the NM will decide when to allow the execution of a queued container. > In order to ensure the instantaneous start of a guaranteed-start container, the NM may decide to pre-empt/kill running queueable containers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)