[LOG4J2-2552] Allow access to the backlog state of the disruptor to improve programatic reconfiguration of async appenders.

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Information Provided
• Component/s: Core
• Assignee: Unassigned
• Reporter: Paul Togher
• Created: 21/Feb/19 16:13
• Updated: 04/Mar/19 10:33
• Resolved: 04/Mar/19 10:33

Description

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.

Issue Links

• links to: GitHub Pull Request #257