[
https://issues.apache.org/jira/browse/FLUME-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734562#comment-13734562
]
Hudson commented on FLUME-2154:
-------------------------------
SUCCESS: Integrated in flume-trunk #488 (See
[https://builds.apache.org/job/flume-trunk/488/])
FLUME-2154. Reducing duplicate events caused by reset-connection-interval
(hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=99db32ccd163daf9d7685f0e8485941701e1133d)
* flume-ng-core/src/main/java/org/apache/flume/sink/AbstractRpcSink.java
* flume-ng-core/src/test/java/org/apache/flume/sink/TestAvroSink.java
> Reducing duplicate events caused by reset-connection-interval
> -------------------------------------------------------------
>
> Key: FLUME-2154
> URL: https://issues.apache.org/jira/browse/FLUME-2154
> Project: Flume
> Issue Type: Improvement
> Reporter: Juhani Connolly
> Assignee: Juhani Connolly
> Priority: Minor
> Attachments: FLUME-2154-2.patch
>
>
> In avro-sink/source it would appear that every time the connection is reset
> some duplicate logs can be generated. I haven't been able to figure out the
> cause of this(they should have been rolled back when the connection gets
> closed by the timer)
> I've put together a patch that serializes the reset. This gets rid of the
> duplicates and shouldn't result in a performance penalty as events sent
> during the reset end up getting reset anyway.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
