[
https://issues.apache.org/jira/browse/KAFKA-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5435:
-------------------------------
Status: Patch Available (was: Open)
> Produce state lost if no snapshot retained
> ------------------------------------------
>
> Key: KAFKA-5435
> URL: https://issues.apache.org/jira/browse/KAFKA-5435
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, core, producer
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Blocker
> Fix For: 0.11.0.0
>
>
> We have an optimization in {{Log}} to avoid the need to scan the log to build
> producer state during the upgrade path. Basically, if no producer snapshot
> exists, then we assume that it's an upgrade and take a new snapshot from the
> end of the log. Unfortunately, it can happen that snapshot files are never
> created or are deleted through truncation. Upon reinitialization, this can
> cause the optimization above to kick in and we lose the current state of all
> producers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
