You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "A. Sophie Blee-Goldman (Jira)" <ji...@apache.org> on 2021/05/01 01:33:00 UTC

[jira] [Created] (KAFKA-12740) 3. Resume processing from last-cleared processor after soft crash

A. Sophie Blee-Goldman created KAFKA-12740:
----------------------------------------------

             Summary: 3. Resume processing from last-cleared processor after soft crash
                 Key: KAFKA-12740
                 URL: https://issues.apache.org/jira/browse/KAFKA-12740
             Project: Kafka
          Issue Type: Sub-task
          Components: streams
            Reporter: A. Sophie Blee-Goldman


Building off of that, we can go one step further and avoid duplicate work within the subtopology itself. Any time a record is partially processed through a subtopology before hitting an error, all of the processors up to that point will be applied again when the record is reprocessed. If we can keep track of how far along the subtopology a record was processed, then we can start reprocessing it from the last processor it had cleared before hitting an error.
This proposal is the most likely to benefit from letting a StreamThread recover after an unexpected exception rather than letting it die and starting up a new one, as we don’t need to worry about handing anything off from the dying thread to its replacement. 




--
This message was sent by Atlassian Jira
(v8.3.4#803005)