Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A1A421058D for ; Fri, 13 Dec 2013 04:47:21 +0000 (UTC) Received: (qmail 83539 invoked by uid 500); 13 Dec 2013 04:47:14 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 83143 invoked by uid 500); 13 Dec 2013 04:47:11 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 83136 invoked by uid 99); 13 Dec 2013 04:47:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Dec 2013 04:47:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of write2kishore@gmail.com designates 209.85.216.46 as permitted sender) Received: from [209.85.216.46] (HELO mail-qa0-f46.google.com) (209.85.216.46) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Dec 2013 04:47:04 +0000 Received: by mail-qa0-f46.google.com with SMTP id f11so436525qae.5 for ; Thu, 12 Dec 2013 20:46:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=shuko2pHE6KlxoEo3cEbxBUw9j7DNH5RWYUJegeejKc=; b=iISQWYI2exkamil3Wvx8YGl5GHLrMuJb/3kW5An+FhqPlpP7PU8uIggB0JzK31L8Nj YMncezPu0iyBCkSYA8YlKmh7064dzeChTYEYkfeuZz2oIx4e/UlftdReOwIIzbdZDa10 jsjfDK6G5ziVmyIj7vBhAjANpLq6/BNV1tZKobif73248kfCRxK3HCH04TXdTzZ0Tyvn ZrCFlH4IbIlZURRwnW+cv5eHzYh7xt7fkDhr35nN1RwopBAPZc12jMFYxn/AVW02dhJa zNZUeDZgz5RFKs00fRsUgslbQK48WaDWr/2duuEIhhL1yNDWzBmK8k3w9AikvrBOXR7w A05w== MIME-Version: 1.0 X-Received: by 10.229.127.193 with SMTP id h1mr1114270qcs.14.1386910003370; Thu, 12 Dec 2013 20:46:43 -0800 (PST) Received: by 10.96.215.100 with HTTP; Thu, 12 Dec 2013 20:46:43 -0800 (PST) In-Reply-To: <20049C46-2DD7-444D-B6DC-4675F4843D25@hortonworks.com> References: <20049C46-2DD7-444D-B6DC-4675F4843D25@hortonworks.com> Date: Fri, 13 Dec 2013 10:16:43 +0530 Message-ID: Subject: Re: Yarn -- one of the daemons getting killed From: Krishna Kishore Bonagiri To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a1133dbce161f4804ed6326b4 X-Virus-Checked: Checked by ClamAV on apache.org --001a1133dbce161f4804ed6326b4 Content-Type: text/plain; charset=ISO-8859-1 No, I am running on 2 node cluster. On Fri, Dec 13, 2013 at 1:52 AM, Vinod Kumar Vavilapalli < vinodkv@hortonworks.com> wrote: > Is all of this on a single node? > > Thanks, > +Vinod > > On Dec 12, 2013, at 3:26 AM, Krishna Kishore Bonagiri < > write2kishore@gmail.com> wrote: > > Hi, > I am running a small application on YARN (2.2.0) in a loop of 500 times, > and while doing so one of the daemons, node manager, resource manager, or > data node is getting killed (I mean disappearing) at a random point. I see > no information in the corresponding log files. How can I know why is it > happening so? > > And, one more observation is that, this is happening only when I am using > "*" for node name in the container requests, otherwise when I used a > specific node name, everything is fine. > > Thanks, > Kishore > > > > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity > to which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. --001a1133dbce161f4804ed6326b4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
No, I am running on 2 node cluster.


On Fri, Dec 13, 2013 at 1:52 A= M, Vinod Kumar Vavilapalli <vinodkv@hortonworks.com> w= rote:
Is all o= f this on a single node?

Thanks,
+Vinod

On Dec 12, 2013, at 3:26 AM, Krishna Kishore Bonagiri <write2kishore@gma= il.com> wrote:

H= i,
=A0 I am running a small application on YARN (2.2.0) in a loop of 500 times= , and while doing so one of the daemons, node manager, resource manager, or= data node is getting killed (I mean disappearing) at a random point. I see= no information in the corresponding log files. How can I know why is it ha= ppening so?

=A0And, one more observation is that, this is happening= only when I am using "*" for node name in the container requests= , otherwise when I used a specific node name, everything is fine.

Thanks,
Kishore


CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u.
--001a1133dbce161f4804ed6326b4--