hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers" <...@cloudera.com>
Subject Re: [DISCUSS] Switch to log4j 2
Date Fri, 15 Aug 2014 15:50:25 GMT
Not necessarily opposed to switching logging frameworks, but I believe we
can actually support async logging with today's logging system if we wanted
to, e.g. as was done for the HDFS audit logger in this JIRA:

https://issues.apache.org/jira/browse/HDFS-5241

--
Aaron T. Myers
Software Engineer, Cloudera


On Fri, Aug 15, 2014 at 5:44 AM, Steve Loughran <stevel@hortonworks.com>
wrote:

> moving to SLF4J as an API is independent —it's just a better API for
> logging than commons-logging, was already a dependency and doesn't force
> anyone to switch to a new log back end.
>
>
> On 15 August 2014 03:34, Tsuyoshi OZAWA <ozawa.tsuyoshi@gmail.com> wrote:
>
> > Hi,
> >
> > Steve has started discussion titled "use SLF4J APIs in new modules?"
> > as a related topic.
> >
> >
> http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201404.mbox/%3CCA+4kjVv_9cMmTDQZCgZy-CHSLyB1WkGdUNXS7wrhesLwbuHJjQ@mail.gmail.com%3E
> >
> > It sounds good to me to use asynchronous logging when we log INFO. One
> > concern is that asynchronous logging makes debugging difficult - I
> > don't know log4j 2 well, but I suspect that ordering of logging can be
> > changed even if WARN or  FATAL are logged with synchronous logger.
> >
> > Thanks,
> > - Tsuyoshi
> >
> > On Thu, Aug 14, 2014 at 6:44 AM, Arpit Agarwal <aagarwal@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.
> >
>
> --
> 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.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message