Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for upgrading Zookeeper and Broker components #65

Open
rmarting opened this issue Jul 26, 2023 · 0 comments
Open

Support for upgrading Zookeeper and Broker components #65

rmarting opened this issue Jul 26, 2023 · 0 comments

Comments

@rmarting
Copy link
Collaborator

SUMMARY

Kafka allows upgrading components with no downtime following a rolling strategy for each component of the Zk+Bk deployment. The collecion should provide the capabillity to upgrade a deployment from one version to another one in a simple way, implementing that strategy.

It is important to keep in mind the versions involved during the upgrade as they define the message format in the kafka topics. Kafka’s log message format version and inter-broker protocol version specify, respectively, the log format version appended to messages and the version of the Kafka protocol used in a cluster. To ensure the correct versions are used, the upgrade process involves making configuration changes to existing Kafka brokers and code changes to client applications (consumers and producers).

NOTE: The collection will not cover the upgrade of the Kafka clients, as they are not part of the Kafka topology.

The collection should identify an upgrade process for a newer version and execute the process described here.

References:

ISSUE TYPE
  • Feature Idea
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant