Reading the below (old) discussion of JCL vs SLF4J made me want to ask
if there is anyone out there who actually makes use of the fact that
logging goes via the commons-logging intermediary? If its not being
used, why not cut to the chase and use log4j directly or what seems to
be just as capable, native java.util.logging. Using the latter would
allow us lose two jars from $HADOOP_HOME/lib and the dynamic changing of
logging levels, HADOOP-1185, could be done w/o addition via JMX when the
JVM had been started with its JMX Agent enabled
Yours,
St.Ack
Torsten Curdt wrote:
On 18.07.2007, at 11:06, Devaraj Das wrote:
Came across this link: http://www.slf4j.org/index.html. Got me
interested
since it makes a remark "SLF4J suffers from none of the class loader
problems or memory leaks observed with Jakarta Commons Logging
(JCL).". Is
it true that the version of commons-logging we use in hadoop could have
issues to do with memory leaks? If so, we should consider moving to
SLF4J
unless there are other issues. There is a well-defined migration path -
http://www.slf4j.org/manual.html#gradual
There have been a few releases since then addressing most of the
problems listed. If you are really concerned I suggest to make sure
you use the latest version and check on the commons dev list if you
have questions.
cheers
--
Torsten
