You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2023/02/21 17:40:00 UTC

[jira] [Resolved] (KAFKA-14530) Check state updater more than once in process loops

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

Matthias J. Sax resolved KAFKA-14530.
-------------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

> Check state updater more than once in process loops
> ---------------------------------------------------
>
>                 Key: KAFKA-14530
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14530
>             Project: Kafka
>          Issue Type: Task
>          Components: streams
>            Reporter: Lucas Brutschy
>            Assignee: Lucas Brutschy
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> In the new state restoration code, the state updater needs to be checked regularly by the main thread to transfer ownership of tasks back to the main thread once the state of the task is restored. The more often we check this, the faster we can start processing the tasks.
> Currently, we only check the state updater once in every loop iteration of the state updater. And while we couldn't observe this to be strictly not often enough, we can increase the number of checks easily by moving the check inside the inner processing loop. This would mean that once we have iterated over `numIterations` records, we can already start processing tasks that have finished restoration in the meantime.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)