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

Have goflow wait for Kafka vs. crash looping #86

Open
leoluk opened this issue Apr 25, 2022 · 1 comment
Open

Have goflow wait for Kafka vs. crash looping #86

leoluk opened this issue Apr 25, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@leoluk
Copy link
Member

leoluk commented Apr 25, 2022

No description provided.

@leoluk leoluk changed the title init container for goflow that waits for Kafka vs. crash looping Have goflow wait for Kafka vs. crash looping Apr 25, 2022
@fionera fionera added the bug Something isn't working label Dec 11, 2022
@fionera
Copy link
Collaborator

fionera commented Dec 11, 2022

I would propose we create our own waiting container since we have to wait for multiple requirements and I don't want to hardcode an external container.

Copied from StackOverflow (https://stackoverflow.com/questions/56115226/test-if-kafka-ready-topics-are-reachable-from-cli) :

We had the same issues, and the current approach we are taking involves several call to the kafka-topic CLI

  • We make sure the topic exists with kafka-topics.sh --describe --topic FOO
  • Check that all partitions have a leader kafka-topics.sh --describe --topic FOO --unavailable-partitions (output should be empty)
  • Check that all partitions are fully replicated kafka-topics.sh --describe --topic FOO --under-replicated-partitions (output should be empty)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants