When while logstash is running one of the kafka pods restarts (and gets a new IP) logstash doesn't renew de ip's which results in a consuming stop on the partition which resides on that pod.
for example: pod 2 was restarted the following warn is shown:
[2019-10-15T13:13:37,101][WARN ][org.apache.kafka.clients.NetworkClient] [Consumer clientId=logstash-0, groupId=logstash-reporting] Connection to node 2 (kafka-2.broker.cts-dev.svc.cluster.local/xxx.xx.103.144:9092) could not be established. Broker may not be available.
the ip xxx.xx.103.144 was the old ip the new ip is xxx.xx.102.179
After logstash loses a broker it should use the bootstrap to resync the ips
When while logstash is running one of the kafka pods restarts (and gets a new IP) logstash doesn't renew de ip's which results in a consuming stop on the partition which resides on that pod.
for example: pod 2 was restarted the following warn is shown: [2019-10-15T13:13:37,101][WARN ][org.apache.kafka.clients.NetworkClient] [Consumer clientId=logstash-0, groupId=logstash-reporting] Connection to node 2 (kafka-2.broker.cts-dev.svc.cluster.local/xxx.xx.103.144:9092) could not be established. Broker may not be available.
the ip xxx.xx.103.144 was the old ip the new ip is xxx.xx.102.179
After logstash loses a broker it should use the bootstrap to resync the ips