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 2020/02/26 22:04:00 UTC

[jira] [Resolved] (KAFKA-9614) Avoid initializing the topology twice when resuming stream tasks from suspended state

     [ https://issues.apache.org/jira/browse/KAFKA-9614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guozhang Wang resolved KAFKA-9614.
----------------------------------
    Fix Version/s: 2.6.0
       Resolution: Fixed

> Avoid initializing the topology twice when resuming stream tasks from suspended state
> -------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9614
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9614
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>            Priority: Major
>             Fix For: 2.6.0
>
>
> When resuming from a suspended stream task, today it first transit to restoring and then to running. The main motivation is to simplify the state transition FSM of stream tasks. We should only call `initializeTopology` when transiting from restoring to running, but the tech debt cleanup missed one gap that beforehand we transit to running directly and hence also call `initializeTopology` at the first transition.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)