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 04883200AF5 for ; Thu, 2 Jun 2016 18:44:01 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0312F160A52; Thu, 2 Jun 2016 16:44:01 +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 4A516160A3E for ; Thu, 2 Jun 2016 18:44:00 +0200 (CEST) Received: (qmail 42511 invoked by uid 500); 2 Jun 2016 16:43: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 42474 invoked by uid 99); 2 Jun 2016 16:43:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jun 2016 16:43:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 415192C1F61 for ; Thu, 2 Jun 2016 16:43:59 +0000 (UTC) Date: Thu, 2 Jun 2016 16:43:59 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5171) Extend DistributedSchedulerProtocol to notify RM of containers allocated by the Node MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 02 Jun 2016 16:44:01 -0000 [ https://issues.apache.org/jira/browse/YARN-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312630#comment-15312630 ] Arun Suresh commented on YARN-5171: ----------------------------------- [~elgoiri], I don't think you are decrementing {{attemptResourceUsageOpportunistic}} when the OPPORTUNISTIC container completes. I guess we would should also have to remove it from the SchedulerApplicationAttempts's liveContainers list. You can do this in the {{completedContainer()}} method in your if check like so: {noformat} if (!rmContainer.isExternallyAllocated()) { completedContainerInternal(rmContainer, containerStatus, event); } else { // get the SchedulerApplicationAttempt // remove from the appAttempts liveContainers // decrement the appAttempts attemptResourceUsageOpportunistic } {noformat} Makes sense ? > Extend DistributedSchedulerProtocol to notify RM of containers allocated by the Node > ------------------------------------------------------------------------------------ > > Key: YARN-5171 > URL: https://issues.apache.org/jira/browse/YARN-5171 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Inigo Goiri > Attachments: YARN-5171.000.patch, YARN-5171.001.patch, YARN-5171.002.patch, YARN-5171.003.patch > > > Currently, the RM does not know about Containers allocated by the OpportunisticContainerAllocator on the NM. This JIRA proposes to extend the Distributed Scheduler request interceptor and the protocol to notify the RM of new containers as and when they are allocated at the NM. The {{RMContainer}} should also be extended to expose the {{ExecutionType}} of the container. -- 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