Finally I copied the hadoop 2.2.0 log4j.properties in place of the HBase
one and got what I was looking for ;)
Thanks for your recommendations.
2013/12/14 Ted Yu
> TRACE,RFA was used in the command you posted - it overrode DEBUG,console in
> your properties file.
>
> I should have mentioned th
TRACE,RFA was used in the command you posted - it overrode DEBUG,console in
your properties file.
I should have mentioned that I got the snippet from
/grid/0/var/log/hbase/hbase.log
where /grid/0/var/log/hbase is the log dir.
You can try specifying TRACE,console
Cheers
On Sat, Dec 14, 2013 at
I have updated the log4.properties.
Here is the output with log4j debug enabled:
hbase@hbasetest1:~$ bin/hbase -Dlog4j.debug
org.apache.hadoop.hbase.util.CompressionTest file:///tmp/test.txt snappy
log4j: Trying to find [log4j.xml] using context classloader
sun.misc.Launcher$AppClassLoader@713c81
How did you set log level to DEBUG ?
I tried the following command and it worked:
hbase -Dhbase.root.logger=DEBUG,RFA
org.apache.hadoop.hbase.util.CompressionTest file:///tmp/test.txt snappy
Snippet of log file:
2013-12-14 15:23:37,853 DEBUG [main] hdfs.BlockReaderLocal: The
short-circuit local
Hi there,
I'm trying this tool:
bin/hbase org.apache.hadoop.hbase.util.CompressionTest file:///tmp/test.txt
snappy
And I want to set the log level to debug to see why it fails. But it seems
that it's not taking the log4j.conf into consideraion. I tried to remove
it, same result. I tried to set to
