Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
From: "Ganelin, Ilya" <Ilya.Ganelin@capitalone.com>
To: "dev@apex.incubator.apache.org" <dev@apex.incubator.apache.org>
Date: Mon, 24 Aug 2015 22:57:08 -0400
Subject: Re: Retrieving logs
Thread-Topic: Retrieving logs
Thread-Index: AdDe4boRCUdvzlo3TCWxnuzvfTA2nA==
Message-ID: <D2012720.CA4F%ilya.ganelin@capitalone.com>
References: <D2010CC2.CA2A%ilya.ganelin@capitalone.com>
 <CABAipVadw8g1AjUELaTwQvyj-E-i2jXwp1JjsNyXzD+O=czTeg@mail.gmail.com>
In-Reply-To: 
 <CABAipVadw8g1AjUELaTwQvyj-E-i2jXwp1JjsNyXzD+O=czTeg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.5.3.150624
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Apologies! This was a half-baked e-mail that I didn=B9t intend to send.

For others=B9 reference, one may also be able to use.

yarn logs -applicationId APP_ID -ContainerId ContainerID to get logs for a
specific container.

One other thing that we=B9re seeing is that the yarn logs are saved by node,
rather than by container.
E.g.
/tmp/logs/yarn_logs/NODE_1
/tmp/logs/yarn_logs/NODE_2

/tmp/logs/yarn_logs/NODE_3


Is this by design? Is there a way to change it so logs are output per
container? This would greatly facilitate debugging since then we would
have a unique log per JVM.

Thank you!

On 8/24/15, 7:53 PM, "Chinmay Kolhatkar" <chinmay@datatorrent.com> wrote:

>Hi,
>
>If you have applicationId of the application you can use following command
>to get all the logs of all the containers:
>
>yarn logs -applicationId <applicationId>
>
>Output of this command will be huge, so you might want to redirect the
>output to a file for analysis.
>
>-Chinmay.
>
>
>On Tue, Aug 25, 2015 at 6:32 AM, Ganelin, Ilya
><Ilya.Ganelin@capitalone.com>
>wrote:
>
>> Hi all =AD we=B9re seeing failures in individual containers and wanted to
>> figure out how to retrieve logs.
>> ________________________________________________________
>>
>> The information contained in this e-mail is confidential and/or
>> proprietary to Capital One and/or its affiliates and may only be used
>> solely in performance of work or services for Capital One. The
>>information
>> transmitted herewith is intended only for use by the individual or
>>entity
>> to which it is addressed. If the reader of this message is not the
>>intended
>> recipient, you are hereby notified that any review, retransmission,
>> dissemination, distribution, copying or other use of, or taking of any
>> action in reliance upon this information is strictly prohibited. If you
>> have received this communication in error, please contact the sender and
>> delete the material from your computer.
>>

________________________________________________________

The information contained in this e-mail is confidential and/or proprietary=
 to Capital One and/or its affiliates and may only be used solely in perfor=
mance of work or services for Capital One. The information transmitted here=
with is intended only for use by the individual or entity to which it is ad=
dressed. If the reader of this message is not the intended recipient, you a=
re hereby notified that any review, retransmission, dissemination, distribu=
tion, copying or other use of, or taking of any action in reliance upon thi=
s information is strictly prohibited. If you have received this communicati=
on in error, please contact the sender and delete the material from your co=
mputer.