Return-Path: X-Original-To: apmail-giraph-user-archive@www.apache.org Delivered-To: apmail-giraph-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 92B591079B for ; Fri, 9 Aug 2013 17:49:00 +0000 (UTC) Received: (qmail 53782 invoked by uid 500); 9 Aug 2013 17:49:00 -0000 Delivered-To: apmail-giraph-user-archive@giraph.apache.org Received: (qmail 53623 invoked by uid 500); 9 Aug 2013 17:48:57 -0000 Mailing-List: contact user-help@giraph.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@giraph.apache.org Delivered-To: mailing list user@giraph.apache.org Received: (qmail 53609 invoked by uid 99); 9 Aug 2013 17:48:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 17:48:56 +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 ashish.sdr@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qc0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 17:48:50 +0000 Received: by mail-qc0-f179.google.com with SMTP id n10so2363950qcx.10 for ; Fri, 09 Aug 2013 10:48:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=4oIqnqSuqzM3JyCnq742pnawSgNPgrkpUEZH0brAL38=; b=ujag4YQjz7pu7BYkAwcKwLQxjslobAQr2v5j+V4gwylRlkgFxmpp350nXoqOr+pFjp SIxDfuDJZKsAfMKbklOJVZpwwfK4w83ZX623PvkIbAT6E8T16900gsaJEDKtzq+5UJZc dS7tv5Z83yqbVKBDCLdKWmbaHEarlD5XoIRParHh6vG3ay5NKHa4dDoED9Pt1YybV+6j UKzvi+LhXt2MlootaYc631de9sHp+DK8KIDgF1/sDZmm0trBzFxX2VQ1aVzk2cMcD8wY bmJlnVj+T2blFySp6SFVA+0u3LxSfJNpzk7aTMUDM7rSPNgR14ihWBKTHeIYxS7576e6 bwWA== X-Received: by 10.224.3.197 with SMTP id 5mr12419407qao.25.1376070509559; Fri, 09 Aug 2013 10:48:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.2.104 with HTTP; Fri, 9 Aug 2013 10:48:09 -0700 (PDT) In-Reply-To: References: From: Ashish Jain Date: Fri, 9 Aug 2013 10:48:09 -0700 Message-ID: Subject: Re: Logger output To: user@giraph.apache.org Content-Type: multipart/alternative; boundary=001a11c24600e885f204e38761eb X-Virus-Checked: Checked by ClamAV on apache.org --001a11c24600e885f204e38761eb Content-Type: text/plain; charset=ISO-8859-1 Hello Marco, In my experiments, I have found the log output to be in the hadoop log file of the application. When you run your application, note down the job number. The hadoop log file is usually in HADOOP_BASE_PATH/logs/userlogs/job_number. In it you need to look at syslog, among the various lines interleaved will be the output of Log. If you run your program on a cluster, you might have to find out on which node was the program run. One way is, if you use -op in your application, look at the log to see the cluster node name. Other way is to just check the HADOOP_BASE_PATH/logs/userlogs/job_number on all the nodes of your cluster. You will find output from the MasterThread and from one/more worker threads. This is the approach I have used, there might be a better way to do this. Hope this helps. Ashish On Fri, Aug 9, 2013 at 4:43 AM, Marco Aurelio Barbosa Fagnani Lotz < m.a.b.lotz@stu12.qmul.ac.uk> wrote: > Hello there! :) > > I am writing a Giraph application but I could not find the output place > for the logs. > Where is the default output path to see the logged info? > > By log I mean the log that is inside a class that one creates: > > private static final Logger LOG = > Logger.getLogger(SimpleBFSComputation.class); > > I call the following method to enable that log to debug: > Log.setLevel(Level.DEBUG); > > And then write some random content in it: > if (LOG.isDebugEnabled){ > LOG.debug("This is a logged line");} > > > Just to clarify, if I called the "Log.setLevel(Level.DEBUG);" I am > enabling the log for debug, and then the method isDebugEnabled will > return true, correct? > > Best Regards, > Marco Lotz > --001a11c24600e885f204e38761eb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Marco,

In my experiments, I have = found the log output to be in the hadoop log file of the application. When = you run your application, note down the job number. The hadoop log file is = usually in HADOOP_BASE_PATH/logs/userlogs/job_number. In it you need to loo= k at syslog, among the various lines interleaved will be the output of Log.=

If you run your program on a cluster, you might have to= find out on which node was the program run. One way is, if you use -op in = your application, look at the log to see the cluster node name. Other way i= s to just check the HADOOP_BASE_PATH/logs/userlogs/job_number on all the no= des of your cluster. You will find output from the MasterThread and from on= e/more worker threads.=A0

This is the approach I have used, there might be a bett= er way to do this. Hope this helps.

Ashish


On Fri, A= ug 9, 2013 at 4:43 AM, Marco Aurelio Barbosa Fagnani Lotz <m.a.b= .lotz@stu12.qmul.ac.uk> wrote:
Hello there! :)

I am writing a Giraph application but I could not find the output place for= the logs.
Where is the default output path to see the logged info?

By log I mean the log that is inside a class that one creates:

private static final Logger LOG =3D
=A0 =A0 =A0 Logger.getLogger(SimpleBFSComputation.class);

I call the following method to enable that log to debug:
Log.setLevel(Level.DEBUG);<= /font>

And t= hen write some random content in it:
if (LOG.isDebugEnabled){
=A0=A0=A0=A0LOG.debug("= ;This is a logged line");}


Just to clarify, if I called the "Log.setLevel(Level.DEBUG);" I am enabling the log for debug, and then the method=A0isDebugEnabl= ed will return true, correct?=A0

Best Regards,
Marco Lotz

--001a11c24600e885f204e38761eb--