monogon-dev/NetMeta

Have goflow wait for Kafka vs. crash looping

leoluk opened this issue · 1 comments

Have goflow wait for Kafka vs. crash looping

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)