Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 07EF310E40 for ; Tue, 11 Mar 2014 05:11:54 +0000 (UTC) Received: (qmail 44048 invoked by uid 500); 11 Mar 2014 05:11:41 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 43717 invoked by uid 500); 11 Mar 2014 05:11:40 -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 43705 invoked by uid 99); 11 Mar 2014 05:11:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 05:11:38 +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 (athena.apache.org: domain of sudhakara.st@gmail.com designates 209.85.219.49 as permitted sender) Received: from [209.85.219.49] (HELO mail-oa0-f49.google.com) (209.85.219.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 05:11:33 +0000 Received: by mail-oa0-f49.google.com with SMTP id g12so8003688oah.36 for ; Mon, 10 Mar 2014 22:11:13 -0700 (PDT) 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=ibZsERXPX0YieR6YwGMPCMbIFTpwYPVHKqeQSHQ7LZ4=; b=etf/qDN0OMeaFqU7v8lH5Ana4Ee6fzgzR41v27S+dZ0Whi2biTeo73Pz7S6I0uy5en ES53qYzFXHvqgjcXdAKe5ZgRbpZnlEnDMa3iQb+jLe8MvQongEqkp7ZoY8kcwGKI3BTE ZrQ1zB4xvk9zvUnn1am47AsFHhHw78sRMoZYFmPKxi3hrpnctNttvoesbhgOgD5pqfei TWwnvOgSEIquuLzcHIm/uHkrh0u1DsjlR+dKYxyvnwN9QeXcbRrETLUdnbwWcGlpSuvc /OzYbHtNCiZnkTI8alhkAXj2QanZQ+vi7s+ElSzQ8ise9EBNngyq6JaR8zAjSOJDsWS4 OeEw== MIME-Version: 1.0 X-Received: by 10.60.115.129 with SMTP id jo1mr27747292oeb.0.1394514672949; Mon, 10 Mar 2014 22:11:12 -0700 (PDT) Received: by 10.76.13.74 with HTTP; Mon, 10 Mar 2014 22:11:12 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Mar 2014 10:41:12 +0530 Message-ID: Subject: Re: Hadoop 2.2.0 not showing progress From: sudhakara st To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e011619b6b71fd804f44dbf0b X-Virus-Checked: Checked by ClamAV on apache.org --089e011619b6b71fd804f44dbf0b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable RM not able schdule your jobs it waiting indefinitely to schedule jobs, may due to not able communicate with NM's or not able create AM or sufiicient resoucrce are not avaialbel in containers etc. Check your configuration for Java heap, yarn.app.mapreduce.am.resource.mb, mapreduce.reduce.memory.mb, mapreduce.map.memory.mb, Check RM web URL for available resources and scheduler information and also check RM,NM logs On Mon, Mar 10, 2014 at 9:54 PM, Xuan Gong wrote: > Hey, Silvina: > > You may find more information about this application from RM web UI or > Yarn Command Line (Type yarn application -help to find out commands). > > Thanks > > Xuan Gong > > > On Mon, Mar 10, 2014 at 4:16 AM, Silvina Ca=EDno Lores < > silvi.caino@gmail.com> wrote: > >> Hi all, >> >> I've been noticing lately that sometimes my Hadoop jobs do not report >> progress in the terminal. They seem like they are stuck at the "Running >> job: job_ ...." message, however YarnChilds are running and properly >> executing. >> >> I know that my job didn't fail but it's very inconvenient not being able >> to monitor how is it going, specially to estimate completion time. This >> doesn't happen all the time, any clues on what is going on? >> >> Thanks in advance, >> Silvina >> > > > 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 th= at > 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 immediate= ly > and delete it from your system. Thank You. --=20 Regards, ...sudhakara --089e011619b6b71fd804f44dbf0b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
RM not able schdule your jobs it waiting indefinitely to s= chedule jobs, may due to=A0 not able communicate with NM's or not able = create=A0 AM or=A0 sufiicient resoucrce are not avaialbel in containers etc= . Check your configuration for Java heap, yarn.app.mapredu= ce.am.resource.mb, mapreduce.reduce.memory.mb, mapreduce.map.memory.mb, Check RM web URL for available= resources and scheduler information and also check RM,NM logs


On Mon, Mar 10, 2014 at 9:54 PM, Xuan Gong <xgong@hortonworks.= com> wrote:
Hey, Silvina:

=A0 =A0You may find more information about this application from RM w= eb UI or Yarn Command Line (Type yarn application -help to find out command= s).

Thanks

Xuan Gong=A0


On Mon, Mar 10, 2014 = at 4:16 AM, Silvina Ca=EDno Lores <silvi.caino@gmail.com> wrote:
Hi all,

I've been noticing lately that sometimes my Hadoop jobs do not report p= rogress in the terminal. They seem like they are stuck at the "Running= job: job_ ...." message, however YarnChilds are running and properly = executing.

I know that my job didn't fail but it's very = inconvenient not being able to monitor how is it going, specially to estima= te completion time. This doesn't happen all the time, any clues on what= is going on?

Thanks in advance,
Silvina


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 comm= unication is strictly prohibited. If you have received this communication i= n error, please contact the sender immediately and delete it from your syst= em. Thank You.


--
=A0 =A0 =A0=A0
= Regards,
...sudhakara
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0
--089e011619b6b71fd804f44dbf0b--