Closed rfrink closed 5 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
When Kubernetes relocates Kafka brokers onto new nodes, often the Kafka cluster becomes inaccessible, and the logs indicate it is still trying to use the OLD Node IPs. Hence, a POD restart is required.
Likewise, with consumers, often they dont get correct META_DATA updates with the new IPs of the Kafka brokers.
Have tried to update the JAVA Network TTL, but, inconsistent results.
Anyway, around this?