Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EDE2E200AF6 for ; Sat, 28 May 2016 01:45:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EC839160A37; Fri, 27 May 2016 23:45:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 436F4160A12 for ; Sat, 28 May 2016 01:45:14 +0200 (CEST) Received: (qmail 17645 invoked by uid 500); 27 May 2016 23:45:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 17634 invoked by uid 99); 27 May 2016 23:45:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2016 23:45:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 39C182C1F60 for ; Fri, 27 May 2016 23:45:13 +0000 (UTC) Date: Fri, 27 May 2016 23:45:13 +0000 (UTC) From: "Konstantinos Karanasos (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-5117) QueuingContainerManager does not start GUARANTEED Container even if Resources are available MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 27 May 2016 23:45:15 -0000 [ https://issues.apache.org/jira/browse/YARN-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-5117: ----------------------------------------- Attachment: YARN-5117.003.patch Getting rid of the {{waitForContainerState}} in the {{TestQueuingContainerManagerImpl}} that was causing timing issues. > QueuingContainerManager does not start GUARANTEED Container even if Resources are available > ------------------------------------------------------------------------------------------- > > Key: YARN-5117 > URL: https://issues.apache.org/jira/browse/YARN-5117 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Konstantinos Karanasos > Attachments: YARN-5117.001.patch, YARN-5117.002.patch, YARN-5117.003.patch > > > When NM Queuing is turned on, it looks like GUARANTEED containers do not start even when there are no containers running on the NM. The following is seen in the logs : > {noformat} > ..... > 2016-05-19 22:34:12,711 INFO [IPC Server handler 0 on 49809] queuing.QueuingContainerManagerImpl (QueuingContainerManagerImpl.java:pickOpportunisticContainersToKill(351)) - There are no sufficient resources to start guaranteed container_1463711648301_0001_01_000001 even after attempting to kill any running opportunistic containers. > ..... > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org