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
- JCL vs SLF4J Devaraj Das
- Re: JCL vs SLF4J Torsten Curdt
