Hi Kenneth, Recently we noticed that there's an issue in the Sarama client's broker address management. Although the Sarama client fetches the latest broker information and stores it in the brokers <https://github.com/IBM/sarama/blob/main/client.go#L155C6-L155C6> list, the seedbrokers <https://github.com/IBM/sarama/blob/main/client.go#L151C5-L151C5> list is never refreshed and it's always the first broker being used <https://github.com/IBM/sarama/blob/main/client.go#L765C11-L765C11>. This has caused two problems for us:
1. The broker hostname might be re-used and the same hostname may be pointing to a broker in another cluster. This will make consumers read from the low watermark for a topic with the same name in the wrong cluster. 2. The client may completely fail the topic discovery and be stuck in group rebalance and unable to consume messages. We are wondering if similar problems are spotted in your usage. Best, Qichao Chu Software Engineer | Data - Kafka [image: Uber] <https://uber.com/> On Mon, Jul 31, 2023 at 10:57 AM Kenneth Eversole <kevers...@cloudflare.com.invalid> wrote: > Hello, > > Xinli, > > I can only speak for Cloudflare, but we use various versions of the Sarama > Go Client for various production workloads and they seem to function quite > well. > > I am curious what your reasoning for wanting to replace Sarama? > > Kenneth Eversole > > On Fri, Jul 28, 2023 at 1:58 PM Xinli shang <sha...@uber.com.invalid> > wrote: > > > Hi all, > > > > We are considering replacing the Sarama Go client with confluent-kafka-go > > <https://github.com/confluentinc/confluent-kafka-go> which is supported > > and > > seems promising. Regarding reliability and performance, does anybody want > > to share the experience? Whether or not it is the experience in > production > > or testing, they are all appreciated. > > > > -- > > Xinli Shang > > >
