I added comments on the JIRA, perhaps best to keep it all in one place in
the JIRA, but I would not recommend making the synchronous route the
default since it results in jumbled log files with events out of order.
This used to be our default and nobody was happy with this. (It is a
nightmare to tr
Absolutely, we already have a "discard" policy that works great! There are
certain types of events that I don't wish to throw away, even under very heavy
load.
See
https://logging.apache.org/log4j/2.x/manual/configuration.html#asyncQueueFullPolicy
-ck
On Fri, May 17, 2019, at 15:02, Gary Greg
Would it make sense to have an optional "drop events on the floor" policy
when things get busy?
Gary
On Fri, May 17, 2019, 14:52 Carter Kozak wrote:
> Hi friends,
>
> I've filed LOG4J2-2606 after tracking down the issue in prod. It's
> frightening because the result was instability across entir
Hi friends,
I've filed LOG4J2-2606 after tracking down the issue in prod. It's frightening
because the result was instability across entire box due to CPU starvation,
caused by a full logging queue from heavy load. I'm curious if anyone else has
run into this behavior. We may want to change the
