[
https://issues.apache.org/jira/browse/KAFKA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16385472#comment-16385472
]
Matthias J. Sax edited comment on KAFKA-6127 at 3/5/18 1:40 AM:
----------------------------------------------------------------
If KAFKA-6608 is resolved, we need to consider how to handle a timeout
exception of {{KafkaConsumer#position()}} within Streams.
was (Author: mjsax):
If KAFKA-6608 is resolve, we need to consider how to handle a timeout exception
of {{KafkaConsumer#position()}} within Streams.
> Streams should never block infinitely
> -------------------------------------
>
> Key: KAFKA-6127
> URL: https://issues.apache.org/jira/browse/KAFKA-6127
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.0
> Reporter: Matthias J. Sax
> Priority: Major
>
> Streams uses three consumer APIs that can block infinite: {{commitSync()}},
> {{committed()}}, and {{position()}}.
> If we block within one operation, the whole {{StreamThread}} would block, and
> the instance does not make any progress, becomes unresponsive (for example,
> {{KafkaStreams#close()}} suffers), and we also might drop out of the consumer
> group.
> We might consider to use {{wakeup()}} calls to unblock those operations to
> keep {{StreamThread}} in a responsive state.
> Note: there are discussion to add timeout to those calls, and thus, we could
> get {{TimeoutExceptions}}. This would be easier to handle than using
> {{wakeup()}}. Thus, we should keep an eye on those discussions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
