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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-9614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045950#comment-17045950 ] 

ASF GitHub Bot commented on KAFKA-9614:
---------------------------------------

guozhangwang commented on pull request #8173: KAFKA-9614: Not initialize topology twice in StreamTask
URL: https://github.com/apache/kafka/pull/8173
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>
> 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)