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

[1.4] Backport using KRaft mode for Kafka #1190

Merged
merged 2 commits into from
Jul 9, 2024

Conversation

fedinskiy
Copy link
Contributor

@fedinskiy fedinskiy commented Jul 1, 2024

Summary

In KRaft mode Zookeper is not used, since brokers communicate to each other directly.
Backports the following PRs:

Please check the relevant options

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Dependency update
  • Refactoring
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Example scenarios has been updated / added
  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@fedinskiy fedinskiy changed the title [1.3] Backport using KRaft mode for Kafka [1.4] Backport using KRaft mode for Kafka Jul 1, 2024
@fedinskiy
Copy link
Contributor Author

run tests

@michalvavrik
Copy link
Contributor

Failure looks related, I'll review when the investigation is done. Thanks

@fedinskiy fedinskiy force-pushed the backport/1.4-kraft branch 2 times, most recently from bebd28d to 7f0268d Compare July 2, 2024 11:42
@michalvavrik
Copy link
Contributor

run tests

@fedinskiy
Copy link
Contributor Author

fedinskiy commented Jul 2, 2024

@michalvavrik to early, I am trying to debug #1186 here, so the CI is just accidentally green :)

In KRaft mode Zookeper is not used, since brokers communicate to each
other directly.
@fedinskiy
Copy link
Contributor Author

run tests

@fedinskiy
Copy link
Contributor Author

fedinskiy commented Jul 9, 2024

Ci failure in jvm build (FromPomXmlStrimziKafkaWithoutRegistryMessagingIT in examples/kafka) is related, but requires strimzi 0.107.0 (which is not released yet)
UPD: same goes for AlertMonitorIT in Kafka-Streams for 3.8.999-SNAPSHOT

Copy link
Contributor

@michalvavrik michalvavrik left a comment

Choose a reason for hiding this comment

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

LGTM

@michalvavrik michalvavrik merged commit 4e04d39 into quarkus-qe:1.4.z Jul 9, 2024
7 of 9 checks passed
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 this pull request may close these issues.

2 participants