This repository has been archived by the owner on Mar 17, 2024. It is now read-only.
Implement backoff strategy for Kafka connections in Kafka Lag Exporter #6
Labels
enhancement
New feature or request
When installed in a fresh cluster Kafka Lag Exporter will fail if configured/discovered Kafka clusters cannot be reached. Kafka Lag Exporter is configured to automatically discover Strimzi Kafka clusters by watching for Kafka CRD’s, but at first install it may detect the Kafka CRD before Kafka has finished coming online, and fail. It won’t attempt to connect again.
The workaround right now is to delete the pod and let its deployment recreate it once the Kafka clusters are online. Since Kafka Lag Exporter can support multiple clusters I would like to add a backoff strategy to connection attempts so it will try to connect to clusters indefinitely.
Logs for kafka-lag-exporter pod:
The text was updated successfully, but these errors were encountered: