logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kamal Bahadur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-693) Flume Persistent Appender Should have a max limit on the number of events in the temp storage
Date Tue, 05 Aug 2014 22:07:16 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kamal Bahadur updated LOG4J2-693:
---------------------------------

      Priority: Major  (was: Minor)
    Issue Type: New Feature  (was: Improvement)

> Flume Persistent Appender Should have a max limit on the number of events in the temp
storage
> ---------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-693
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-693
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Appenders, Flume Appender
>            Reporter: Kamal Bahadur
>         Attachments: patch_LOG4J2-693.txt
>
>
> We use flume appender with persistent option. If flume agent becomes not accessible for
some reason, the appender should stop accepting logs and throw exception instead of continuing
to accept events and then run out of disk space.
> A max limit option on the number of events yet to be processed will be help full. This
will ensure that we will never exceed the number of events stored on disk.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message