[
https://issues.apache.org/jira/browse/FLUME-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726265#comment-15726265
]
Hudson commented on FLUME-3031:
-------------------------------
UNSTABLE: Integrated in Jenkins build Flume-trunk-hbase-1 #235 (See
[https://builds.apache.org/job/Flume-trunk-hbase-1/235/])
FLUME-3031. Change sequence source to reset its counter for event body (bessbd:
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=2ff2dbbd13db5de747c654ef132c98941cdd45dc])
* (edit)
flume-ng-core/src/main/java/org/apache/flume/source/SequenceGeneratorSource.java
* (edit)
flume-ng-core/src/test/java/org/apache/flume/source/TestSequenceGeneratorSource.java
* (edit) flume-ng-doc/sphinx/FlumeUserGuide.rst
> sequence source should reset its counter for event body on channel exception
> ----------------------------------------------------------------------------
>
> Key: FLUME-3031
> URL: https://issues.apache.org/jira/browse/FLUME-3031
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources, Test
> Affects Versions: v1.7.0
> Reporter: Attila Simon
> Assignee: Attila Simon
> Fix For: v1.8.0
>
>
> SequenceGeneratorSource uses a counter to construct the body of the generated
> Events which counter is not reseted when writing event to channel failed.
> This can lead to a situation that the total number of unique events at
> destination (if deduplication relies on msg body) is bigger than the
> totalEvents configuration parameter due to the retries.
> Fix should make sure that number of events at destination after filtering out
> the duplicates is equal to the configured value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
