Doing (ii) would be an isolated app-level config and wouldn't get affected by the toggling of (i). The feature from (i) is available already in CDH 4.0.0-b2 btw.
On Fri, May 4, 2012 at 4:58 AM, Mapred Learn <mapred.le...@gmail.com> wrote: > Hi Harsh, > > Does doing (ii) mess up with hadoop (i) level ? > > Or does it happen in both the options anyways ? > > > Thanks, > -JJ > > On Fri, Apr 20, 2012 at 8:28 AM, Harsh J <ha...@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.le...@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 >> -- Harsh J
