You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by GitBox <gi...@apache.org> on 2019/03/01 14:41:11 UTC

[GitHub] ptogher opened a new pull request #257: LOG4J2-2552 Allow access to the backlog state of the disruptor to improve program…

ptogher opened a new pull request #257: LOG4J2-2552 Allow access to the backlog state of the disruptor to improve program…
URL: https://github.com/apache/logging-log4j2/pull/257
 
 
   …atic reconfiguration of async appenders.
   
   This change is to help support programmatically switching async appenders. In cases where it is important that logged messages go to the appender that was configured at the time of writing the log event, the flushing the appender buffer to disk is not sufficient, as the log events may still be in the disruptor. This change provides access to test if the disruptor has items in its backlog. This becomes useful in an application that is controlling its logging config and logging events to ensure that no new logging events are generated between removing one appender and adding another, so that it can also ensure the change does not happen until all pending log events are processed.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services