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.3] Backport using KRaft mode for Kafka #1189

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.

Backport of #1175

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/kraft 1.3 [1.3] Backport using KRaft mode for Kafka Jul 1, 2024
@fedinskiy fedinskiy force-pushed the backport/kraft-1.3 branch 2 times, most recently from 3af6979 to a1154bf Compare July 1, 2024 15:04
@michalvavrik
Copy link
Member

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

@fedinskiy fedinskiy force-pushed the backport/kraft-1.3 branch 2 times, most recently from 1a78571 to 92a95e8 Compare July 3, 2024 11:23
@fedinskiy
Copy link
Contributor Author

run tests

1 similar comment
@michalvavrik
Copy link
Member

run tests

@michalvavrik
Copy link
Member

Kafka OpenShift failures look related, please have a look.

In KRaft mode Zookeper is not used, since brokers communicate to each
other directly.
Adds detailed output and hopefully fixes this error:
quarkus-qe#1186
@michalvavrik
Copy link
Member

run tests

@michalvavrik michalvavrik merged commit fa56c60 into quarkus-qe:1.3.z Jul 9, 2024
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