You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Walker Carlson (Jira)" <ji...@apache.org> on 2020/12/09 02:34:00 UTC
[jira] [Commented] (KAFKA-9638) Do not trigger REBALANCING when
specific exceptions occur in Kafka Streams
[ https://issues.apache.org/jira/browse/KAFKA-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246252#comment-17246252 ]
Walker Carlson commented on KAFKA-9638:
---------------------------------------
There is a kip that might effect how this issues behaves. With the new handler (KIP-671) there will be an option to just shutdown the application on such failures. This should prevent unnecessary rebalances in this case. It would be left in state ERROR which the following kip is making terminal.
[https://cwiki.apache.org/confluence/x/lCvZCQ]
> Do not trigger REBALANCING when specific exceptions occur in Kafka Streams
> ---------------------------------------------------------------------------
>
> Key: KAFKA-9638
> URL: https://issues.apache.org/jira/browse/KAFKA-9638
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Reporter: Levani Kokhreidze
> Priority: Major
>
> As of now, when StreamThread encounters exception in Kafka Streams application, it will result in REBALANCING of all the tasks that were responsibility of the given thread. Problem with that is, if the exception was, lets say some logical exception, like NPE, REBALANCING is pretty much useless, cause all other threads will also die with the same NPE. This kind of mute rebalancing gives extra costs in terms of network traffic, IOPS, etc in case of large stateful applications.
> In addition, this behaviour causes global outage of the Kafka Streams application, instead of localized outage of the certain tasks. Would be great if Kafka Streams users could specify via some interface, exceptions that must not trigger rebalancing of the tasks. StreamThread may still die, but in this case, we would have isolated incident.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)