You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bruno Cadonna (Jira)" <ji...@apache.org> on 2021/12/09 14:40:00 UTC

[jira] [Assigned] (KAFKA-10199) Separate state restoration into separate threads

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

Bruno Cadonna reassigned KAFKA-10199:
-------------------------------------

    Assignee: Bruno Cadonna  (was: Guozhang Wang)

> Separate state restoration into separate threads
> ------------------------------------------------
>
>                 Key: KAFKA-10199
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10199
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Bruno Cadonna
>            Priority: Major
>
> As part of the restoration optimization effort, we would like to move the restoration process to separate threads such that:
> 1. Stream threads would not be restricted by the main consumer `poll` frequency to keep as part of the group.
> 2. We can allow larger batches of data to be written into the restoration.
> Besides this, we'd also like to fix the known issues that for piggy-backed source topics as changelog topics, the serde exception / extra processing logic would be skipped.
> We would also cleanup the global update tasks as part of this effort to consolidate to the separate restoration threads, and would also gear them up with corresponding monitoring metrics (KIPs in progress).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)