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

feat(dev): Upgrade zookeeper/kafka dev containers for Intel hosts #29293

Merged
merged 1 commit into from
Oct 15, 2021

Conversation

armenzg
Copy link
Member

@armenzg armenzg commented Oct 13, 2021

In #28574, we upgraded the versions of zookeeper/kafka to 6.x only for Apple
arm64 hosts.

When trying to use such version on Intel, it would fail because version 6.x
requires specifying the path to data absolutely (see docs), otherwise, you would get this
error:

Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED !

If you don't rename the key of the moount bind, users with an existing set-up would not get
the absolue path properly configured, thus, they would still face the issue (see comment).
In other words, people starting from scratch would have no issues.

At the time, we decided to back things out and investigate later.

This change reunites Intel and arm64 hosts.

In #28574, we upgraded the versions of zookeeper/kafka to 6.x only for Apple
arm64 hosts.

When trying to use such version on Intel, it would fail because version 6.x
requires specifying the path to `data` *absolutely* (see [docs][docs]), otherwise, you would get this
error:

> Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED !

If you don't rename the key of the moount bind, users with an existing set-up would not get
the absolue path properly configured, thus, they would still face the issue (see [comment][comment]).
In other words, people starting from scratch would have no issues.

At the time, we decided to back things out and investigate later.

This change reunites Intel and arm64 hosts.

[docs]: https://docs.confluent.io/platform/current/installation/docker/operations/external-volumes.html#data-volumes-for-kafka-and-zk
[comment]: #28574 (comment)
@armenzg armenzg self-assigned this Oct 13, 2021
@armenzg armenzg added the Component: Developer Environment This covers issues related to setting up a developer's environment label Oct 13, 2021
"environment": {"ZOOKEEPER_CLIENT_PORT": "2181"},
"volumes": {"zookeeper": {"bind": "/var/lib/zookeeper"}},
"volumes": {"zookeeper_6": {"bind": "/var/lib/zookeeper/data"}},
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing the key is what allows users that come from version 5.x to not require a fresh set up.

@armenzg armenzg marked this pull request as ready for review October 13, 2021 18:30
@armenzg
Copy link
Member Author

armenzg commented Oct 13, 2021

@avgupta456 would you mind testing it locally?

@armenzg armenzg requested a review from BYK October 14, 2021 12:35
Copy link
Member

@BYK BYK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@armenzg
Copy link
Member Author

armenzg commented Oct 15, 2021

We are not using v6 for on-premise so kind of blind-accepting.

FYI, with this version, we can drop zookeeper:

* https://www.confluent.io/blog/kafka-without-zookeeper-a-sneak-peek/

* https://github.com/apache/kafka/blob/6d1d68617ecd023b787f54aafc24a4232663428d/config/kraft/README.md

I'm aware of that. I've added it to the backlog.

@armenzg armenzg merged commit 321701d into master Oct 15, 2021
@armenzg armenzg deleted the armenzg/dev/newer-kafka branch October 15, 2021 12:40
@github-actions github-actions bot locked and limited conversation to collaborators Oct 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Component: Developer Environment This covers issues related to setting up a developer's environment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants