Using asynchronous loggers for improved performance sounds reasonable. However, IMO we already log too much at INFO level (particularly YARN). Logging more at DEBUG level and lowering the overhead of enabling DEBUG logging is preferable.
One concern is the defaults. Based on what I read on the log4j2 page shared, we might want to keep our audit logging synchronous and make all other logging asynchronous. Is there a way to easily configure it this way; otherwise, what is the dev cost we are looking at? On Wed, Aug 13, 2014 at 2:44 PM, Arpit Agarwal <aagar...@hortonworks.com> wrote: > I don't recall whether this was discussed before. > > I often find our INFO logging to be too sparse for useful diagnosis. A high > performance logging framework will encourage us to log more. Specifically, > Asynchronous Loggers look interesting. > https://logging.apache.org/log4j/2.x/manual/async.html#Performance > > What does the community think of switching to log4j 2 in a Hadoop 2.x > release? > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
