[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Commented] (LOG4J2-693) Flume Persistent Appender Should have a max limit on the number of e
From:       "Kamal Bahadur (JIRA)" <jira () apache ! org>
Date:       2014-06-26 19:00:27
Message-ID: JIRA.12723931.1403807050978.56024.1403809227796 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/LOG4J2-693?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=14045018#comment-14045018 ] 

Kamal Bahadur commented on LOG4J2-693:
--------------------------------------

I will work on this and will send you the patch.

> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]