[jira] [Commented] (LOG4J2-2048) Increase default queue size for AsyncAppender

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165435#comment-16165435 ] 

ASF subversion and git services commented on LOG4J2-2048:
---------------------------------------------------------

Commit a0e946de5411cc16d56a9bb5eb2a6aa62caaac53 in logging-log4j2's branch refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a0e946d ]

LOG4J2-2048 Increase default queue size for AsyncAppender from 128 to 1024.


> Increase default queue size for AsyncAppender
> ---------------------------------------------
>
>                 Key: LOG4J2-2048
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2048
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 2.9.0
>            Reporter: Remko Popma
>            Assignee: Remko Popma
>             Fix For: 2.9.1
>
>
>  LOG4J2-2031 highlighted that the default queue size (128) for AsyncAppender is extremely small compared to the async logger defaults.
> Even small event bursts will likely fill up the queue and cause messages to appear in the log file out of order. Until LOG4J2-2031 is fixed, a larger queue size will make this less likely to happen.
> Better recursion detection (see LOG4J2-2031) will fix the out-of-sequence messages. From that point, when the queue is full the logging call will block until a slot in the queue becomes available, so the only impact of a small queue is performance. From a performance perspective it is also desirable to have a default queue size of something like 1K slots to handle moderate-size bursts of events smoothly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)