[
https://issues.apache.org/jira/browse/LOG4J2-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064329#comment-14064329
]
Kamal Bahadur commented on LOG4J2-693:
--------------------------------------
I finished coding the actual change. I am trying to create unit test where I
use a bogus hostname in the config file so that worker thread fails to consume
data from berkeley db and the number of events in the db reaches the max limit.
I am able to capture that and throw LoggingException. The problem is that the
unit test just hangs there. I think it is trying to connect to the bogus
hostname and is waiting to timeout. Any ideas on how I can update the unit test
so that I dont have to wait for ever for the unit test to finish?
> 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: Improvement
> Components: Appenders
> Reporter: Kamal Bahadur
> Priority: Minor
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
