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/05/12 20:08:04 UTC

[jira] [Work started] (KAFKA-5186) Avoid expensive initialization of producer state when upgrading

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

Work on KAFKA-5186 started by Jason Gustafson.
----------------------------------------------
> Avoid expensive initialization of producer state when upgrading
> ---------------------------------------------------------------
>
>                 Key: KAFKA-5186
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5186
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Critical
>             Fix For: 0.11.0.0
>
>
> Currently the producer state is always loaded upon broker initialization. If we don't find a snapshot file to load from, then we scan the log segments from the beginning to rebuild the state. Of course, when users upgrade to the new version, there will be no snapshot file, so the upgrade could be quite intensive. It would be nice to avoid this by assuming instead that the absence of a snapshot file means that the producer state should start clean and we can avoid the expensive scanning.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)