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 97778200BD5 for ; Thu, 8 Dec 2016 09:26:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 96040160B1F; Thu, 8 Dec 2016 08:26:00 +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 DE65C160B1E for ; Thu, 8 Dec 2016 09:25:59 +0100 (CET) Received: (qmail 38428 invoked by uid 500); 8 Dec 2016 08:25:59 -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 38408 invoked by uid 99); 8 Dec 2016 08:25:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2016 08:25:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B30702C03EE for ; Thu, 8 Dec 2016 08:25:58 +0000 (UTC) Date: Thu, 8 Dec 2016 08:25:58 +0000 (UTC) From: "Hitesh Sharma (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5292) NM Container lifecycle and state transitions to support for PAUSED container state. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 08 Dec 2016 08:26:00 -0000 [ https://issues.apache.org/jira/browse/YARN-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731526#comment-15731526 ] Hitesh Sharma commented on YARN-5292: ------------------------------------- Hi [~kasha], the design doc and the patch allow an opportunistic container to be paused and resumed. The actual implementation of the pluggable interface will be as part of [YARN-5196] and there via yarn-site.xml you can specify the preemption policy for an opportunistic container when there is a guaranteed container waiting to run (i.e. pause or kill). Currently only the NM scheduler can raise the PAUSE/RESUME events and there is no support for doing so in the container management protocol. One of the questions on the table is if there is a need to extend support of PAUSE/RESUME to guaranteed containers and have the AMs initiate that. Would love to hear some thoughts on that and if there are any use cases that can benefit from that. > NM Container lifecycle and state transitions to support for PAUSED container state. > ----------------------------------------------------------------------------------- > > Key: YARN-5292 > URL: https://issues.apache.org/jira/browse/YARN-5292 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Hitesh Sharma > Assignee: Hitesh Sharma > Attachments: YARN-5292.001.patch, YARN-5292.002.patch, YARN-5292.003.patch, YARN-5292.004.patch, YARN-5292.005.patch, yarn-5292.pdf > > > This JIRA addresses the NM Container and state machine and lifecycle changes needed to support pausing. -- 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