[
https://issues.apache.org/jira/browse/KAFKA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534708#comment-15534708
]
Vahid Hashemian commented on KAFKA-4234:
----------------------------------------
[~hachikuji] I read the comments on
[KAFKA-3491|https://issues.apache.org/jira/browse/KAFKA-3491] and it seems
there is no consensus on which way to go. Has it been decided that calling
{{unsubscribe}} before {{close}} should be the workaround? If so, are we ok
with the issues that not committing offsets in {{unsubscribe}} will bring back
(e.g. reading duplicates)?
> Consumer should not commit offsets in unsubscribe()
> ---------------------------------------------------
>
> Key: KAFKA-4234
> URL: https://issues.apache.org/jira/browse/KAFKA-4234
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Jason Gustafson
> Fix For: 0.10.1.0
>
>
> In KIP-70, we changed the behavior of {{unsubscribe}} to commit offsets if
> autocommit is enabled. Unfortunately, because of the issue documented in
> KAFKA-3491, this makes it impossible to abort processing if an exception is
> thrown while processing some records. Until we have a fix for this problem,
> we should probably revert this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
