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 7795F200B34 for ; Sat, 18 Jun 2016 03:33:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 763DA160A63; Sat, 18 Jun 2016 01:33:07 +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 BD38F160A61 for ; Sat, 18 Jun 2016 03:33:06 +0200 (CEST) Received: (qmail 99556 invoked by uid 500); 18 Jun 2016 01:33:05 -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 99495 invoked by uid 99); 18 Jun 2016 01:33:05 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Jun 2016 01:33:05 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 5AB8B2C1F61 for ; Sat, 18 Jun 2016 01:33:05 +0000 (UTC) Date: Sat, 18 Jun 2016 01:33:05 +0000 (UTC) From: "Konstantinos Karanasos (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: Sat, 18 Jun 2016 01:33:07 -0000 [ https://issues.apache.org/jira/browse/YARN-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337407#comment-15337407 ] Konstantinos Karanasos commented on YARN-5171: ---------------------------------------------- .bq Solution (1) is simpler. While solution (2) seems cleaner Correcting myself: I meant solution (2) is simpler, but (1) is cleaner... > 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, YARN-5171.004.patch, YARN-5171.005.patch, YARN-5171.006.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