On Wed, Jul 22, 2015 at 8:01 AM, kusmanjali kushmanj...@gmail.com wrote:
1. Most of the logging frame works use a log forwarder + queue
mechanism(Logstash, Fluectd) to store logs into database. What is the
advantage of using this over using Log4j NoSQL appenders to write directly
to the
I just tried it and it produces the same error.
column.layout.toSerializable(event) always produces a non-null String
because it is based on a StringBuilder.
So I don't think there is even a way for the code to set a column to NULL,
it will always be set to the Strings or NULL, even if I write
I am not familiar with Logstash or Fluentd, but I am familiar with Apache Flume.
Log4j 2 provides capabilities to write directly to a SQL or some NoSQL
databases. Some users prefer to do this, but it does have some risk as to what
to do if the target destination becomes unavailable. As Remko
Yes, Spark seems to have its own shutdown hook and it logs stuff from
within there.
If I put shutdownHook=disable in my log4j2.xml, the problem goes away.
But then I guess that Log4j is never shut down properly?
On Wed, Jul 22, 2015 at 8:39 AM, Ralph Goers ralph.go...@dslextreme.com
wrote:
The
That is correct, but if you only log to files that may not be so bad. If you
use any asynchronous stuff or things that buffer events then that would be a
problem.
Ralph
On Jul 22, 2015, at 2:41 AM, Mikael Ståldal mikael.stal...@magine.com wrote:
Yes, Spark seems to have its own shutdown
I agree with what you are saying here, but there is one other thing I would
like to add.
One of my motivations for starting work on Log4j 2 was that my employer had a
need for a very flexible audit logging system. Most applications I am aware of
do their auditing to a database. However, we
Our idea is to build a central logging system just by using Log4 and doing
away with forwarders and queues.
Don't ypu notice that your giving your own answer? Use of a forwarder
and a queue is (IMO) the obvious choice for a central logging system,
based on existing components, and with
