kafka-go

kafka-go copied to clipboard

WriteMessages can force metadata updates when occur NotLeaderForPartition error

1

WriteMessages will retry , when occur NotLeaderForPartition error, this mean the client's metadata are likely out of date. Is it possible to force trigger metadata updates? Instead of relying only...

zydovech

Upgrade to Go 1.18. This is a prerequisite for https://github.com/segmentio/kafka-go/pull/1247 as that PR introduces generics to the kafka-go codebase We needed to bump the go linter image used in CI...

petedannemann

logger: ensure compatibility with new log/slog package

4

The API for the logger changes only slightly and should continue to be backwards compatible for any existing code.

kevinburkesegment

New consumer group no topic and assignment problem

6

Hello, first of all, thank you for this great library. Recently, we deploy a new consumer group for an already-existent topic (v0.4.38). But we cannot consume messages at all. **Kafka...

Abdulsametileri

Allow setting the windowsize for zstd compression for greater memory control.

petedannemann

How do producers obtain the partition and offset of message sending

2

How do producers obtain the partition and offset of message sending

guozhao-coder

`reader.Close()` stuck randomly

1

### Problem This does not happen all the time. Maybe 1 out of 5 or 10 times. We have consumer application with following Reader config: ``` kafkaReaderConfig := kafka.ReaderConfig{ Brokers:...

sumerc

getting frequent non-zero number of bytes remaining error during DescribeGroups

5

**Describe the bug** Got non-zero number of bytes remaining: 10 **Kafka Version** > * What version(s) of Kafka are you testing against? v0.4.39 > * What version of kafka-go are...

tarun-discovery

The new log/slog package makes it easier to provide structured logs, which are easier to parse. While this package is available in go 1.21 and up there is a corresponding...

kevinburkesegment

Multiple Broker addresses are configured, but when one of them is unavailable, the client does not try to connect to other available Brokers.

2

**Describe the bug** multiple Broker addresses are configured, but when one of them is unavailable, the client does not try to connect to other available Brokers. **Kafka Version** kafka_2.13-2.6.2 kafka-go:...

JimYJ