[jira] [Work logged] (LOG4J2-2552) Allow access to the backlog state of the disruptor to improve programatic reconfiguration of async appenders.

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2552?focusedWorklogId=202027&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-202027 ]

ASF GitHub Bot logged work on LOG4J2-2552:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Feb/19 16:14
            Start Date: 21/Feb/19 16:14
    Worklog Time Spent: 10m 
      Work Description: ptogher commented on issue #257: LOG4J2-2552 Allow access to the backlog state of the disruptor to improve program…
URL: https://github.com/apache/logging-log4j2/pull/257#issuecomment-466060684
 
 
   Have raised a Jira, if that helps... LOG4J2-2552
 
----------------------------------------------------------------
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


Issue Time Tracking
-------------------

            Worklog Id:     (was: 202027)
            Time Spent: 10m
    Remaining Estimate: 0h

> Allow access to the backlog state of the disruptor to improve programatic reconfiguration of async appenders.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-2552
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2552
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Paul Togher
>            Priority: Trivial
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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 message was sent by Atlassian JIRA
(v7.6.3#76005)