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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: streams
• Assignee: Guozhang Wang
• Reporter: Guozhang Wang
• Created: 26/Feb/20 20:10
• Updated: 26/Feb/20 22:03
• Resolved: 26/Feb/20 22:03

Description

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.

Issue Links

• links to: GitHub Pull Request #8173