_ksco
New discovery: Observed that the groupID created by NewConsumerGroup is not found by ListGroups after some time(few min).
msk config auto.create.topics.enable=false default.replication.factor=3 min.insync.replicas=2 num.io.threads=8 num.network.threads=5 num.partitions=1 num.replica.fetchers=2 replica.lag.time.max.ms=30000 socket.receive.buffer.bytes=102400 socket.request.max.bytes=104857600 socket.send.buffer.bytes=102400 unclean.leader.election.enable=true zookeeper.session.timeout.ms=18000
When I shut down the consumers run, after a while, the `ListGroups` can't look up the consumers groupID, cloudwatch always can't create the groupid After closing the single reader, the...
`RetentionTime` in `ReaderConfig` and `ConsumerGroupConfig` use the library's default settings `ConsumerGroupConfig` is set to 24 hours * 7, but it's the same as before
@achille-roussel Not for the time being, I follow up because of other things to give up the tracking
see see this [example](https://pkg.go.dev/github.com/segmentio/kafka-go#example-Generation.Start-ConsumerGroupParallelReaders )
> > see see this [example](https://pkg.go.dev/github.com/segmentio/kafka-go#example-Generation.Start-ConsumerGroupParallelReaders) > > this example is for consumer group, not for standalone consumer try https://github.com/segmentio/kafka-go/blob/v0.4.32/conn.go#L962 ?
https://github.com/segmentio/kafka-go/blob/v0.4.32/reader.go#L363
Can't you set the GroupID?
I feel that kafka, unlike redis pub/sub, still places more emphasis on the concept of groups