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 default policy to use the synchronous route rather than enqueue. This would allow for contention in other places, and allow certain threadlocals to be initialized on application threads rather than being confined to the background thread, however we already account for this when running in synchronous mode and the current failure is pretty nasty.
Thoughts or concerns? https://issues.apache.org/jira/browse/LOG4J2-2606 Thanks, -ck
