[jira] [Updated] (KAFKA-15308) Wipe Stores upon OffsetOutOfRangeException in ALOS

["Matthias J. Sax (Jira)" <ji...@apache.org>]

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

Matthias J. Sax updated KAFKA-15308:
------------------------------------
    Affects Version/s:     (was: 3.4.0)
                           (was: 3.5.0)

> Wipe Stores upon OffsetOutOfRangeException in ALOS
> --------------------------------------------------
>
>                 Key: KAFKA-15308
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15308
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 3.3.0
>            Reporter: Colt McNealy
>            Priority: Minor
>
> As per this [Confluent Community Slack Thread|https://confluentcommunity.slack.com/archives/C48AHTCUQ/p1690843733272449?thread_ts=1690663361.858559&cid=C48AHTCUQ], Streams currently does not wipe away RocksDB state upon encountering an `OffsetOutOfRangeException` in ALOS.
>  
> `OffsetOutOfRangeException` is a rare case that occurs when a standby task requests offsets that no longer exist in the topic. We should wipe the store for three reasons:
>  # Not wiping the store can be a violation of ALOS since some of the now-missing offsets could have contained tombstone records.
>  # Wiping the store has no performance cost since we need to replay the entirety of what's in the changelog topic anyways.
>  # I have heard (not yet confirmed myself) that we wipe the store in EOS anyways, so fixing this bug could remove a bit of complexity from supporting EOS and ALOS.



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