You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2015/06/18 20:21:00 UTC
[jira] [Commented] (LOG4J2-1056) delayseconds configuration is not
correctly flume avro manager
[ https://issues.apache.org/jira/browse/LOG4J2-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592257#comment-14592257 ]
Ralph Goers commented on LOG4J2-1056:
-------------------------------------
My presumption is that the fix for this would require a background thread. We have discussed having a general purpose background worker thread but have not implemented that yet. I wouldn't want to implement a thread specifically for this.
> delayseconds configuration is not correctly flume avro manager
> --------------------------------------------------------------
>
> Key: LOG4J2-1056
> URL: https://issues.apache.org/jira/browse/LOG4J2-1056
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Siva Kotipalli
> Labels: flumeappender
>
> As per current implementation delaySeconds check is done during call of append method, this may create an issue in the below scenario:
> For example batch size is 1000 and delay secs is 10 mins, assuming we got 990 events continuously and it may take another 1 hr for receiving the next event, then the transfer of the data will not be done for 1 hr even though the delay is 10 mins.
> With the new implementation, batchevents will be transferred if there is not events available for the configured delay secs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org