You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/07/08 15:48:11 UTC
[jira] [Updated] (KAFKA-3938) Fix consumer session timeout issue in
Kafka Streams
[ https://issues.apache.org/jira/browse/KAFKA-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang updated KAFKA-3938:
---------------------------------
Labels: architecture (was: )
> Fix consumer session timeout issue in Kafka Streams
> ---------------------------------------------------
>
> Key: KAFKA-3938
> URL: https://issues.apache.org/jira/browse/KAFKA-3938
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Labels: architecture
>
> After KIP-62 / KAFKA-3888 is merged in, Kafka Streams should leverage this new feature to fix the session timeout issue that can be caused by:
> 1. long rebalance period due to state store restoration.
> 2. exceptional long processing time for a batch of records.
> Also we need to consider:
> 1. state store directory locking mechanism between rebalances while one instance is grabbing tasks from another instance on the same machine.
> 2. exceptional handling in Kafka Streams: what should we really expose to users and what should be handled automatically?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)