Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-4815 Idempotent/transactional Producer (KIP-98)
  3. KAFKA-5186

Avoid expensive initialization of producer state when upgrading

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hachikuji Jason Gustafson
            hachikuji Jason Gustafson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment