kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apurva Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5186) Avoid expensive initialization of producer state when upgrading
Date Thu, 18 May 2017 17:52:04 GMT

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

Apurva Mehta updated KAFKA-5186:
--------------------------------
    Labels: exactly-once  (was: )

> 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: Blocker
>              Labels: exactly-once
>             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)

Mime
View raw message