[
https://issues.apache.org/jira/browse/FLINK-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529504#comment-15529504
]
ASF GitHub Bot commented on FLINK-4702:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2559
Thanks @tzulitai for looking at this. I will leave the offset then as it is
(fixed via followup) and
The Kafka 0.8 connector needs a similar change. This here is encountered by
a user, so I wanted to get the 0.9 fix in faster. Will do a follow-up for Kafka
0.8. Will also correct the issue tag ;-)
I have no good idea how to test this, though, so any thoughts there are
welcome!
> Kafka consumer must commit offsets asynchronously
> -------------------------------------------------
>
> Key: FLINK-4702
> URL: https://issues.apache.org/jira/browse/FLINK-4702
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector
> Affects Versions: 1.1.2
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Blocker
> Fix For: 1.2.0, 1.1.3
>
>
> The offset commit calls to Kafka may occasionally take very long.
> In that case, the {{notifyCheckpointComplete()}} method blocks for long and
> the KafkaConsumer cannot make progress and cannot perform checkpoints.
> Kafka 0.9+ have methods to commit asynchronously.
> We should use those and make sure no more than one commit is concurrently in
> progress, to that commit requests do not pile up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
