hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark question <markq2...@gmail.com>
Subject Re: How to add debugging to map- red code
Date Fri, 20 Apr 2012 18:53:50 GMT
I'm interested in this too, but could you tell me where to apply the patch
and is the following the right command to write it:

 <https://issues.apache.org/jira/secure/attachment/12416955/MAPREDUCE-336_0_20090818.patch>patch
< MAPREDUCE-336_0_20090818.patch<https://issues.apache.org/jira/secure/attachment/12416955/MAPREDUCE-336_0_20090818.patch>

Thank you,
Mark

On Fri, Apr 20, 2012 at 8:28 AM, Harsh J <harsh@cloudera.com> wrote:

> Yes this is possible, and there's two ways to do this.
>
> 1. Use a distro/release that carries the
> https://issues.apache.org/jira/browse/MAPREDUCE-336 fix. This will let
> you avoid work (see 2, which is same as your idea)
>
> 2. Configure your implementation's logger object's level in the
> setup/setConf methods of the task, by looking at some conf prop to
> decide the level. This will work just as well - and will also avoid
> changing Hadoop's own Child log levels, unlike the (1) method.
>
> On Fri, Apr 20, 2012 at 8:47 PM, Mapred Learn <mapred.learn@gmail.com>
> wrote:
> > Hi,
> > I m trying to find out best way to add debugging in map- red code.
> > I have System.out.println() statements that I keep on commenting and
> uncommenting so as not to increase stdout size
> >
> > But problem is anytime I need debug, I Hv to re-compile.
> >
> > If there a way, I can define log levels using log4j in map-red code and
> define log level as conf option ?
> >
> > Thanks,
> > JJ
> >
> > Sent from my iPhone
>
>
>
> --
> Harsh J
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message