[
https://issues.apache.org/jira/browse/KAFKA-7480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-7480:
---------------------------------
Labels: needs-kip new-streams-runtime-should-fix (was: needs-kip)
> GlobalThread should honor custom auto.offset.reset policy
> ---------------------------------------------------------
>
> Key: KAFKA-7480
> URL: https://issues.apache.org/jira/browse/KAFKA-7480
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Navinder Brar
> Priority: Major
> Labels: needs-kip, new-streams-runtime-should-fix
>
> With KAFKA-6121 we improved Kafka Streams resilience and correctness with
> regard to consumer auto.offset.reset and state cleanup.
> Back than, we decided to let GlobalStreamThread die and not handle
> InvalidOffsetException during regular processing, because this error
> indicates a fatal issue and the user should be notified about it. However, as
> reported on the user mailing list, the only thing a user can do is, to
> restart the application (and investigate the root cause). During restart, the
> state will be cleaned up and bootstrapped correctly.
> Thus, we might want to allow users to specify a more resilient configuration
> for this case and log an ERROR message if the error occurs. To ensure
> consistency, we might not allow to set reset policy "latest" though (need
> discussion)? By default, we can still keep "none" and fail.
> Note: `Topology.addGlobalStore` does not allow to set a reset policy. Thus,
> this might require a KIP to extend `Topology.addGlobalStore` accordingly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
