You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thanks for creating this tool. It's a big improvement over a simple TCP listener check.
I'm running into a sporadic issue where, when I reboot my Kafka cluster, one of the nodes' kafka-health-check daemon will just stall without doing anything. Here's the only log output I see:
time="2018-04-30T09:43:33Z" level=info msg="using topic broker-2-health-check for broker 2 health check"
time="2018-04-30T09:43:33Z" level=info msg="using topic broker-2-health-check for broker 2 replication check"
time="2018-04-30T09:43:38Z" level=info msg="unable to connect to broker, retrying in 5s (cannot connect)"
time="2018-04-30T09:43:43Z" level=info msg="unable to connect to broker, retrying in 5s (cannot connect)"
time="2018-04-30T09:45:08Z" level=info msg="using topic broker-2-health-check for broker 2 health check"
time="2018-04-30T09:45:08Z" level=info msg="using topic broker-2-health-check for broker 2 replication check"
Note that the 09:45 time stamp is when I manually restarted my supervisord service that runs kafka-health-check.
This issue only occurs after I have an initially healthy cluster, and then being rolling out an update across the cluster. Notably, each replacement Kafka broker retains the same broker-id, so I'm wondering if that's what's tripping up kafka-health-check?
First, thanks for creating this tool. It's a big improvement over a simple TCP listener check.
I'm running into a sporadic issue where, when I reboot my Kafka cluster, one of the nodes'
kafka-health-check
daemon will just stall without doing anything. Here's the only log output I see:Note that the
09:45
time stamp is when I manually restarted my supervisord service that runskafka-health-check
.This issue only occurs after I have an initially healthy cluster, and then being rolling out an update across the cluster. Notably, each replacement Kafka broker retains the same broker-id, so I'm wondering if that's what's tripping up
kafka-health-check
?Here's the command I'm using to run it:
And of course this works fine on other Kafka brokers. If it's any help, here's my Kafka broker config:
Any help is much appreciated!
The text was updated successfully, but these errors were encountered: