Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
35661: changefeedccl: hook up kafka producer library logs to our logging r=nvanbenschoten a=danhhz I don't entirely love this, given that we don't have much control over sarama's log volume, but sarama returns the same "kafka: client has run out of available brokers to talk to (Is your cluster reachable?)" error for any connection issue. Which means it's basically impossible to debug kafka connection issues without something like this and I think it's better than the alternative of nothing. Motivated by #35510 which makes hard to debug connection issues even more likely. Logs look something like this: I190312 18:56:53.535646 585 vendor/github.com/Shopify/sarama/client.go:123 [kafka-producer] Initializing new client I190312 18:56:53.535714 585 vendor/github.com/Shopify/sarama/client.go:724 [kafka-producer] client/metadata fetching metadata for all topics from broker localhost:9092 I190312 18:56:53.536730 569 vendor/github.com/Shopify/sarama/broker.go:148 [kafka-producer] Connected to broker at localhost:9092 (unregistered) I190312 18:56:53.537661 585 vendor/github.com/Shopify/sarama/client.go:500 [kafka-producer] client/brokers registered new broker #0 at 172.16.94.87:9092 I190312 18:56:53.537686 585 vendor/github.com/Shopify/sarama/client.go:170 [kafka-producer] Successfully initialized new client Release note (enterprise change): `CHANGEFEED`s using kafka log information to help debug connection issues Co-authored-by: Daniel Harrison <[email protected]>
- Loading branch information