Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5DDAA18E99 for ; Thu, 3 Mar 2016 01:26:05 +0000 (UTC) Received: (qmail 57020 invoked by uid 500); 3 Mar 2016 01:26:04 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 56948 invoked by uid 500); 3 Mar 2016 01:26:04 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 56918 invoked by uid 99); 3 Mar 2016 01:26:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Mar 2016 01:26:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BF8F2C023E; Thu, 3 Mar 2016 01:26:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.821 X-Spam-Level: X-Spam-Status: No, score=-0.821 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id bafW8JZyuWFJ; Thu, 3 Mar 2016 01:26:03 +0000 (UTC) Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id E85DB5F341; Thu, 3 Mar 2016 01:26:02 +0000 (UTC) Received: by mail-ob0-f174.google.com with SMTP id rt7so6654069obb.3; Wed, 02 Mar 2016 17:26:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=qS8VuVujVO51yshuez9EhtjX6wye5LZ3Qp16erdxf+k=; b=cvPBDYZ791w6F+5Bh0umOZpYq5iqk+wOJDFQgZYklDb49n7EOa9mRrEsLV8MBsyL4p 4AywiRL1MkIqIUSCH7CDabrr+n1Od0Ts3Q6/rcpPkIai9vI3a0hBsHW4Jr4+5GpNj0r9 l7b+y5dVQ838MJUPJ0VGglZL29Nsx5myqMm6CW+xvlIBkBdmONesXuwEqNHxDG4ORIGN MIs8QNktz1efLNVrf+PQyEnv5gyiVKA9aO1ACBgCe8BlGhRbe7HWsnn1poYMUIXK70/g nszsWYRZRTXSfxApmmhG933kniSJMVwuwUb2DyKa09fzBxuXO5nmm6qwAY6geGRHk522 yMeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=qS8VuVujVO51yshuez9EhtjX6wye5LZ3Qp16erdxf+k=; b=azio1KMN9zQp5Doj/nFKvNCACBblrWfKnA51gK9AxhkEZ20Ehbz0p0/TMXQiFSaZf1 1oG7Ud039tDOVXJuIpdtHt6hHizSVSGzP8Jn/hqIfl3tFdETB+Uhd0Sl8eJbzey7e6J/ vL7NT9dytnQY/kDuyT4VC5IvgutR61HFsVkTVylcz75ms2maQpER7Lmxq0f38rUCSMe6 nimf+AY0rIVan2hL/+OnN41Bla1iTZu8SbAVqLInINCEUElk6bGnChRUa3iZ60UOgSu1 cVt5k1srxOgTm84mbK0AtQLB9aSOcfZG2cx0KaKnX1ulNx+eqUhi+r+2eGGWEnuOPaHY j1/Q== X-Gm-Message-State: AD7BkJLLGzf/fYxOi/t0rueD+zg3kzlcnnpuWxD5Db729ZZdrSTro0C8RwqqL+WDr92jCMWb4chPyxNkYKmAJw== MIME-Version: 1.0 X-Received: by 10.60.135.98 with SMTP id pr2mr24421572oeb.65.1456968362353; Wed, 02 Mar 2016 17:26:02 -0800 (PST) Received: by 10.60.83.237 with HTTP; Wed, 2 Mar 2016 17:26:02 -0800 (PST) Date: Wed, 2 Mar 2016 17:26:02 -0800 Message-ID: Subject: Question about YARN NodeManager and ApplicationMaster failures From: Sadystio Ilmatunt To: user@hadoop.apache.org, yarn-dev@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 Hello, I have some questions regarding failure of NodeManager and Application Master. What happens if NodeManager which is running on the same node as Application Master fails? Does Application Master fail as well? Also How is Application Master failure handled with respect to its (child) container? Do these containers fail too? If Yes, is there a way these containers can be assigned to new instance of application master that might come up on some other node?