Dear Kafka Community we are facing an Issue with kafka-console-consumer.sh / kafka-console-producer.sh (which both use the native java client) and the bootstrap behavior in conjunction with haproxy.
Behavior: After the bootsrap process the java client doesn't disconnect and just keeps the bootstrapping socket open which result in a client disconnect (cD) from haproxy after two minutes. The haproxy documentation states for that cD message "The client did not read any data for as long as the ‘clitimeout’ delay". In our case that’s a problem because during application startup there will be a lot of unneeded connections blocking resources on the proxy. Expected behavior: The Java Client does the bootstrap and disconnects. Our connection path for bootstrapping: Java Client ↔ haproxy ↔ bootstrap url of kafka running with strimzi on kubernetes. After bootstrapping the client connects directly to the brokers and the initial bootstrap connection is not used any more. Is that a known issue / expected behavior? Regards Stefan
