Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 93143 invoked from network); 15 Apr 2011 18:23:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Apr 2011 18:23:53 -0000 Received: (qmail 45741 invoked by uid 500); 15 Apr 2011 18:23:51 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 45524 invoked by uid 500); 15 Apr 2011 18:23:50 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 45516 invoked by uid 99); 15 Apr 2011 18:23:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Apr 2011 18:23:50 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HK_RANDOM_ENVFROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of billmcn@gmail.com designates 209.85.220.176 as permitted sender) Received: from [209.85.220.176] (HELO mail-vx0-f176.google.com) (209.85.220.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Apr 2011 18:23:45 +0000 Received: by vxa37 with SMTP id 37so3742082vxa.35 for ; Fri, 15 Apr 2011 11:23:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=cHKBhv4vaxDPEup2njGilfjdAJpLrhmQTCmApdd/fCE=; b=CqsCFnJ3dUQj3ZWAIasgVzlTar0V4yTR6FBI6aKuloCaANfdRAi+7cWoWqFh+sztAG DYxRdyDrVzfeZAVnDeNEUJV12fXD1ZHry6hXoDkICbT89M6gLQNoDcMqZp7gCoXnvG6E hc0aeGpE2Vk6j/6gCZjPQKp7h3Y9csSwt7rps= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=P1Oa8+XFA+AkT/sXNQKma0mQ7qGS9p/kohq1u1Ty74bRYyEh04GQqdfzLrzyCn2lRy h7AnD6PI1VYmMHG6ilQkJWY1zYlSObgUImCAk8gtkgx62tINmobgut+/SlCt/F0V8Jjl 912Ii0kYXPtno0e5iY0Bmbse6VywxmczL5r0w= MIME-Version: 1.0 Received: by 10.220.173.80 with SMTP id o16mr706765vcz.102.1302891804961; Fri, 15 Apr 2011 11:23:24 -0700 (PDT) Received: by 10.220.105.138 with HTTP; Fri, 15 Apr 2011 11:23:24 -0700 (PDT) In-Reply-To: <4DA60CF5.6070105@darose.net> References: <4DA60CF5.6070105@darose.net> Date: Fri, 15 Apr 2011 11:23:24 -0700 Message-ID: Subject: Re: How to change logging level for an individual job From: "W.P. McNeill" To: common-user@hadoop.apache.org Cc: David Rosenstrauch Content-Type: multipart/alternative; boundary=0016e68def6c372b5404a0f92308 --0016e68def6c372b5404a0f92308 Content-Type: text/plain; charset=UTF-8 I was running into the same problem with Log4J and Hadoop. Even Log4J's package granularity wasn't what I wanted because I wanted to run one instance of MyJob at INFO level and another instance of MyJob at DEBUG level on the same cluster. I ended up letting the caller specify the logging level via a configuration parameter. The setup() function then reads this parameter and does something like the following: Level level = Level.toLevel(configuration.get("custom.loglevel", "INFO")); logger.setLevel(level); On Wed, Apr 13, 2011 at 1:52 PM, David Rosenstrauch wrote: > Is it possible to change the logging level for an individual job? (As > opposed to the cluster as a whole.) E.g., is there some key that I can set > on the job's configuration object that would allow me to bump up the logging > from info to debug just for that particular job? > > Thanks, > > DR > --0016e68def6c372b5404a0f92308--