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

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/06/12 16:34:00 UTC

[jira] [Created] (KAFKA-5435) Produce state lost if no snapshot retained

Jason Gustafson created KAFKA-5435:
--------------------------------------

             Summary: 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
            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)