David Bergman
David Bergman
Interested in this issue. I'm experiencing it with: Sarama version v1.37.2 Go version 1.18 Confluent Cloud Kafka
HI @erangaeb I am experiencing the same issue , was working fine with version v1.29.1 and below, but its failing with the latest version v1.30.0 of Sarama if you update...
experiencing the same issue with sarama v1.37.2 connecting to Confluent cloud kafka instances. write: broken pipe
@Leorfk did you find a solution to this issue? %6|1674804678.385|FAIL|rdkafka#consumer-4| [thrd:GroupCoordinator]: GroupCoordinator: ###.aws.confluent.cloud:9092: Disconnected (after 6283468ms in state UP) Also running this in an ECS container I am getting this...
hi @edenhill I enabled logging "Cgrp, broker", I changed our cluster name to just kafka.eu-west-1.aws.confluent.cloud:9092) in the logs below I included the logs a minute or so before the failure...
issue continues with sarama v1.38.1... write tcp ... write: broken pipe
perhaps with the backing of IBM this issue can finally be addressed ? using v1.38.2-0.20230327141928-9127f1c432c0
I am still experiencing this issue with the latest sarama v1.38.2-0.20230327141928-9127f1c432c0 periodically , so once every week or so, when it seems Confluent Kafka does some rolling upgrades on the...
its happening to me with the latest version of sarama v1.43.1 , @nearih did you ever figure out a resolution?
hi @billygout , just out of interest, are you connecting to a self managed cluster or a Confluent Cloud Cluster? I am connected to a Confluent cluster, and it appears...