Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 E1415104B2 for ; Fri, 28 Feb 2014 18:19:20 +0000 (UTC) Received: (qmail 71086 invoked by uid 500); 28 Feb 2014 18:19:12 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 70865 invoked by uid 500); 28 Feb 2014 18:19:12 -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 70858 invoked by uid 99); 28 Feb 2014 18:19:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 18:19:11 +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 xgong@hortonworks.com designates 209.85.216.178 as permitted sender) Received: from [209.85.216.178] (HELO mail-qc0-f178.google.com) (209.85.216.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 18:19:04 +0000 Received: by mail-qc0-f178.google.com with SMTP id i8so1146507qcq.23 for ; Fri, 28 Feb 2014 10:18:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=FTWSgLwAci3DINAKS+Qf6qfKb1836yfp4bJGNO309/Y=; b=WbXTx12I1vc4I8AIa3fX3eGxsezwYg92ZHoZAFGBWoJy3TnL2Vv5l4shBO81Y3DXpV JWwBQGl2MRMZd/84dfemF7ne3oje7EM9NcUaZJZlLzyWA2/ZApiATPPfnIwGrTH7dZ8a Xv2HjYITggdMpbAF1zj8wHOmvq1Pt0WS+Djrod3iFzz9JWFATdYypObpWHxej6X/LWyF /1g1b78BiaYTAUG2Rh8Qg35TBBttFj8klSihyGsxq3nMtf1x7rTlDAQ+tyO6o2E0Bt/R RmcTOH3EubShdwoZ9nEfd0m34RiYHK+hzXt/HPpvfaDpWVSQXGEIWxC5sJl9Gc5yPf1W OAMg== X-Gm-Message-State: ALoCoQn8PR5i+jX+vd7hB7ibqDzYgYuoc4S1L+32hWPxW4QUhoZHHj8yg9+roo6W6gDPWyVHUV9HH8c8hkCyNDtGNdzKK1YWE6gCZp+uZOJbxGU2j9rbvQU= MIME-Version: 1.0 X-Received: by 10.229.56.200 with SMTP id z8mr5781654qcg.1.1393611522882; Fri, 28 Feb 2014 10:18:42 -0800 (PST) Received: by 10.140.49.49 with HTTP; Fri, 28 Feb 2014 10:18:42 -0800 (PST) In-Reply-To: References: Date: Fri, 28 Feb 2014 10:18:42 -0800 Message-ID: Subject: Re: YARN -- Debug messages in logs From: Xuan Gong To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a113308a4c6cf5004f37b772c X-Virus-Checked: Checked by ClamAV on apache.org --001a113308a4c6cf5004f37b772c Content-Type: text/plain; charset=US-ASCII Hey, Kishore: you can change the log level from INFO to DEBUG in log4j.properties Thanks, Xuan Gong On Fri, Feb 28, 2014 at 10:09 AM, Krishna Kishore Bonagiri < write2kishore@gmail.com> wrote: > Hi, > > How can I get the debug log messages from RM and other daemons? > > For example, > > Currently I could see messages from LOG.info() only, i.e. something > like this: > > LOG.info(event.getContainerId() + " Container Transitioned from " + > oldState + " to " + getState()); > > How can I get those from LOG.debug() ? I mean the following kind of > messages ... > > LOG.debug("Processing " + event.getContainerId() + " of type " + > event.getType()); > > > 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. --001a113308a4c6cf5004f37b772c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hey,=A0Kishore:

=A0 =A0 you can change the log level from INFO to DEBU= G in log4j.properties

Tha= nks,

Xuan Gong


On Fri, Feb 28, 2014 at 10:09 AM, Krishna Kishore Bonagir= i <write2kishore@gmail.com> wrote:
Hi,

=A0 How ca= n I get the debug log messages from RM and other daemons?

For example,

=A0 =A0Currently I could see messages= from LOG.info() only, i.e. something like this:

=A0 =A0 LOG.info(event.getContainerId() + " C= ontainer Transitioned from " + oldState + " to " + getState(= ));

How can I get those from LOG.debug()= ? I mean the following kind of messages ...

=A0 =A0 LOG.debug("Processing " + event.= getContainerId() + " of type " + event.getType());

=

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. --001a113308a4c6cf5004f37b772c--