[
https://issues.apache.org/jira/browse/FLUME-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324601#comment-15324601
]
Hudson commented on FLUME-2920:
-------------------------------
FAILURE: Integrated in Flume-trunk-hbase-1 #160 (See
[https://builds.apache.org/job/Flume-trunk-hbase-1/160/])
FLUME-2920: Kafka Channel Should Not Commit Offsets When Stopping (jarcec:
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=f46bee03eb2c9094aa192dd6b82a494cb26eef35])
*
flume-ng-channels/flume-kafka-channel/src/main/java/org/apache/flume/channel/kafka/KafkaChannel.java
*
flume-ng-channels/flume-kafka-channel/src/test/java/org/apache/flume/channel/kafka/TestKafkaChannel.java
> Kafka Channel Should Not Commit Offsets When Stopping
> -----------------------------------------------------
>
> Key: FLUME-2920
> URL: https://issues.apache.org/jira/browse/FLUME-2920
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.6.0
> Reporter: Kevin Conaway
> Assignee: Kevin Conaway
> Priority: Critical
> Fix For: v1.7.0
>
> Attachments: FLUME-2920.patch
>
>
> The Kafka channel commits the consumer offsets when shutting down (via stop()
> -> decommissionConsumerAndRecords())
> This can lead to data loss if the channel is shut down while messages have
> been fetched in a transaction but the transaction has not yet been committed.
> The only time that the offsets should be committed is when a transaction is
> complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
