[ https://issues.apache.org/jira/browse/KAFKA-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605911#comment-17605911 ]
Guozhang Wang commented on KAFKA-10575: --------------------------------------- Hello [~nicktelford] thanks for your inputs! Yes I'm now thinking about introducing a new API to the `StateRestoreListener` for the paused scenarios, and to create a KIP for that new API as well as a couple correlating metrics changes that will be introduced by KAFKA-10199. Regarding the TaskStateChangeListener, I think it worth a separate discussion thread for its own scope --- personally I think only very advanced users would be leverage on this since {{Tasks}} are a concept that Streams library wants to more or less abstract away from common users: they should not worry too much about the unit of parallelism afterall. > StateRestoreListener#onRestoreEnd should always be triggered > ------------------------------------------------------------ > > Key: KAFKA-10575 > URL: https://issues.apache.org/jira/browse/KAFKA-10575 > Project: Kafka > Issue Type: Improvement > Components: streams > Reporter: Guozhang Wang > Assignee: highluck > Priority: Major > > Today we only trigger `StateRestoreListener#onRestoreEnd` when we complete > the restoration of an active task and transit it to the running state. > However the restoration can also be stopped when the restoring task gets > closed (because it gets migrated to another client, for example). We should > also trigger the callback indicating its progress when the restoration > stopped in any scenarios. -- This message was sent by Atlassian Jira (v8.20.10#820010)