-
Notifications
You must be signed in to change notification settings - Fork 107
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
[UPGRADE] Upgrade component to the latest version: Zookeeper #1853
Comments
Please verify if:
|
Please see task #1137 - Kafka Upgrade. After Kafka 3.0 release Zookeeper probably will not be needed for Kafka. |
Lets upgrade to 3.5.8. |
@mkyc why 3.5.8 and not 3.6.2 - the latest one? |
Hmmmm ... there was some reason @plirglo gave that version in discussion, but I do not remember that reason. |
Upgraded to 3.5.8 done in PR #1897 |
@plirglo Can You comment why to version 3.5.8 not to latest one? I think that the information in kafka release was leading the decision : link Zookeeper in latest version 3.6.2 could be nice . @plirglo Do You have any significant knowledge about it? If not I can make upgrade to latest version in mentioned PR #1897 |
After the discussion about the target version, can we backport this change to previous Epi versions? |
@rpudlowski93 I just based on Kafka documentation link, where stands that Kafka 2.6.0 goes with Zookeeper 3.5.8. Maybe Zookeeper 3.6.2 also will be compatible, but 'm not sure and we need additional test if we want to use this version. |
In my opinion, we can stay with 3.5.8 how the documentation say, PR for the upgrade was already merged. @rafzei Yes, we can backport it to previous version of epiphany but only when upgrade Kafka is backported. It should go together. Kafka 2.6.0 must work with Zookeeper in at least 3.5.8 version. |
@rpudlowski93 I will create issues to backport Kafka. |
Checked: |
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Additional context
If possible, do an improvements in Zookeeper role. 👍
The text was updated successfully, but these errors were encountered: