You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/11/10 21:14:00 UTC
[jira] [Commented] (KAFKA-6122) Global Consumer should handle
TimeoutException
[ https://issues.apache.org/jira/browse/KAFKA-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248038#comment-16248038 ]
ASF GitHub Bot commented on KAFKA-6122:
---------------------------------------
GitHub user mjsax opened a pull request:
https://github.com/apache/kafka/pull/4206
KAFKA-6122: Global Consumer should handle TimeoutException
Implements KIP-224:
- adding new StreamsConfig `retires`
- uses `retires` and `retry.backoff.ms` to handle TimeoutException in GlobalStateManager
- adds two new tests to trigger TimeoutException in global consumer
- uses `retires` and `retry.backoff.ms` for state directory locking
- some minor code cleanup to reduce number of parameters we need to pass around
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mjsax/kafka kafka-6122-global-consumer-timeout-exception
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/4206.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4206
----
commit 8ed6197ad96d359dace78f60b0fbbf080eca5e09
Author: Matthias J. Sax <ma...@confluent.io>
Date: 2017-11-10T21:02:46Z
KAFKA-6122: Global Consumer should handle TimeoutException
----
> Global Consumer should handle TimeoutException
> ----------------------------------------------
>
> Key: KAFKA-6122
> URL: https://issues.apache.org/jira/browse/KAFKA-6122
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.0
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Labels: needs-kip, streams-exception-handling, streams-resilience
> Fix For: 1.1.0, 1.0.1
>
>
> Global consumer does not handle {{TimeoutException}} that might be throw by {{partitonsFor()}} and {{endOffsets()}}. This affect the bootstrapping phase only.
> We need to allow for a proper retry strategy, with configurable max number of retries and back off time between retries. We might need to introduce new configuration parameters -- for this case, we need to do a KIP.
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-224%3A+Add+configuration+parameters+%60retries%60+and+%60retry.backoff.ms%60+to+Streams+API
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)