I finally figured out. It is in the "Definitive Guide" (2nd edition) Ch.
10 Administration/Monitoring/logging. Every daemons use the same
log4j.properties file in the default $HADOOP_HOME/conf directory. However,
one can change the log level dynamically in the web interface. In every
daemon'
diemac.com
Financial Engineering
Freddie Mac
Joey Echeverria
02/29/2012 10:45 PM
Please respond to
mapreduce-user@hadoop.apache.org
To
"mapreduce-user@hadoop.apache.org"
cc
"mapreduce-user@hadoop.apache.org"
Subject
Re: no log function for map/red
uojun_...@freddiemac.com
> Financial Engineering
> Freddie Mac
>
>
>GUOJUN Zhu
>02/27/2012 11:34 AM
>
>Please respond to
> mapreduce-user@hadoop.apache.org
>
> To
> "mapreduce-user@hadoop.apache.org"
> cc
> Subject
> no log functi
571-3824370
guojun_...@freddiemac.com
Financial Engineering
Freddie Mac
GUOJUN Zhu
02/27/2012 11:34 AM
Please respond to
mapreduce-user@hadoop.apache.org
To
"mapreduce-user@hadoop.apache.org"
cc
Subject
no log function for map/red in a cluster setup
Hi.
We are
Hi.
We are testing hadoop. We are using hadoop (0.20.2-cdh3u3). I am using
the cotomized conf directory with -"-config mypath". I modified the
log4j.properties file in this path, adding "
log4j.logger.com.mycompany=DEBUG". It works fine with our
pseudo-one-node-cluster setup (1.00). But
