You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "A. Sophie Blee-Goldman (Jira)" <ji...@apache.org> on 2021/03/25 02:22:00 UTC

[jira] [Resolved] (KAFKA-5256) Non-checkpointed state stores should be deleted before restore

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

A. Sophie Blee-Goldman resolved KAFKA-5256.
-------------------------------------------
    Resolution: Fixed

Closing this since the described behavior is now implemented in EOS and this seems to cover the desired semantics

> Non-checkpointed state stores should be deleted before restore
> --------------------------------------------------------------
>
>                 Key: KAFKA-5256
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5256
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.1
>            Reporter: Tommy Becker
>            Priority: Major
>
> Currently, Kafka Streams will re-use an existing state store even if there is no checkpoint for it. This seems both inefficient (because duplicate inserts can be made on restore) and incorrect (records which have been deleted from the backing topic may still exist in the store). Since the contents of a store with no checkpoint are unknown, the best way to proceed would be to delete the store and recreate before restoring.



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