Improve error handling when Kafka topics don't exist #8219
Closed
+431
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In production environments, the topic auto-creation is disabled by default. That means before someone can deploy a Core, Minion and Sentinel pod, all the topics need to be created by hand manually.
As a monitoring engineer, I would like to know what topics with the correct instance ID prefix have to be created. If Kafka topics can’t be created I should get a reasonable error message on startup, telling me what is necessary to troubleshoot it.