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 799C818884 for ; Fri, 4 Mar 2016 09:56:41 +0000 (UTC) Received: (qmail 93876 invoked by uid 500); 4 Mar 2016 09:56:41 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 93827 invoked by uid 500); 4 Mar 2016 09:56:41 -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 93772 invoked by uid 99); 4 Mar 2016 09:56:41 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Mar 2016 09:56:41 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 000FC2C1F56 for ; Fri, 4 Mar 2016 09:56:40 +0000 (UTC) Date: Fri, 4 Mar 2016 09:56:40 +0000 (UTC) From: "Junping Du (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (YARN-4758) Enable discovery of AMs by containers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4758?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-4758: -------------------------------- Assignee: Junping Du > Enable discovery of AMs by containers > ------------------------------------- > > Key: YARN-4758 > URL: https://issues.apache.org/jira/browse/YARN-4758 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Vinod Kumar Vavilapalli > Assignee: Junping Du > > {color:red} > This is already discussed on the umbrella JIRA YARN-1489. > Copying some of my condensed summary from the design doc (section 3.2.10.= 3) of YARN-4692. > {color} > Even after the existing work in Work=C2=ADpreserving AM restart (Section = 3.1.2 / YARN-1489), we still haven=E2=80=99t solved the problem of old runn= ing containers not knowing where the new AM starts running after the previo= us AM crashes. This is a specifically important problem to be solved for lo= ng running services where we=E2=80=99d like to avoid killing service contai= ners when AMs fail=C2=ADover. So far, we left this as a task for the apps, = but solving it in YARN is much desirable. [(Task) This looks very much like= service=C2=AD-registry (YARN-913), but for app=C2=ADcontainers to discover= their own AMs. > Combining this requirement (of any container being able to find their AM = across fail=C2=ADovers) with those of services (to be able to find through = DNS where a service container is running - YARN-4757) will put our registry= scalability needs to be much higher than that of just service end=C2=ADpoi= nts. This calls for a more distributed solution for registry readers somet= hing that is discussed in the comments section of YARN-1489 and MAPREDUCE-6= 608. > See comment https://issues.apache.org/jira/browse/YARN-1489?focusedCommen= tId=3D13862359&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comme= nt-tabpanel#comment-13862359 -- This message was sent by Atlassian JIRA (v6.3.4#6332)