build(deps): bump the franz-go group across 1 directory with 3 updates

[dependabot]

Bumps the franz-go group with 2 updates in the / directory: github.com/twmb/franz-go and github.com/twmb/franz-go/pkg/kadm.

Updates github.com/twmb/franz-go from 1.20.7 to 1.21.1

Changelog

Sourced from github.com/twmb/franz-go's changelog.

v1.21.1

This patch release contains a few bug fixes in the new share consumer and a few internal improvements. The highlights are noted below; if you are interested in all the improvements, check the commits.

• Share consuming no longer panics on empty batches from the broker.

• The share acking previously did not work in tandem with Record.Recycle; that has been fixed. Records that are recycled without being ack'd are now also auto-accepted.

• PurgeFetchTopics no longer panics on KIP-848 consumer groups.

• ListGroups and ListTransactions fan out to every broker and merge the responses. During a group-coordinator or transaction state leader migration, the same group or transactional ID can transiently appear in both the old and new coordinator's response, producing duplicates in the merged result. The merges now dedupe by key (first shard response wins).

• Two narrow producer logic races have been fixed; the code previously auto-fixed after some time and there were no correctness issues, but now the logic race has been eliminated.

• Azure Event Hubs (and any other broker that advertises high Produce / OffsetFetch / OffsetCommit versions while capping Metadata below v10) is now handled correctly. Previously, OffsetFetch v8/v9 responses were spuriously stamped with UNKNOWN_TOPIC_OR_PARTITION client-side, and Produce v13 / OffsetFetch v10+ / OffsetCommit v10+ could be sent with zero TopicIDs on the wire. The Produce path now caps at v12 if any partition lacks a TopicID, and OffsetFetch / OffsetCommit now pin to v9 in the same situation. Fixes #1312.

Relevant commits

• 3c1d0d2e b7463fd8 7bb7ccbc improvement kgo: add guards across Produce / OffsetFetch / OffsetCommit for brokers that advertise high request versions while capping Metadata below v10 (Azure Event Hubs); fixes #1312
• c606410e bugfix (and other stuff) kgo: simplify share-consumer ack tracking, fix pool-reuse race
• 2ff493a1 kgo: consumer-path audit fixes
• 1623daba kgo: produce path audit fixes
• e7bed5fc improvement kgo: dedupe groups and txns in fan-out sharders
• 96a14015 improvement kgo: consume-path alloc reductions and log-level gates

v1.21.0

This is a relatively "major" minor release. It adds support for Kafka 4.2, adds full support for [KIP-932 share groups][KIP-932], adds [KIP-881 rack-aware partition assignment][KIP-881], adds a handful of other

... (truncated)

Commits

• 963be6f Merge pull request #1316 from twmb/misc
• eae16c2 changelog: note Event Hubs / metadata-v9 guards; remove unreleased note
• 7bb7ccb kgo: pin OffsetFetch and OffsetCommit to v9 when any topic lacks a TopicID
• b7463fd kgo: cap Produce at v12 when any partition lacks a TopicID
• 3c1d0d2 kgo: skip OffsetFetch topic-id resolution below v10
• f3fd99a Merge pull request #1317 from warpstreamlabs/cupcicm/pr/2
• b2aa603 Update my github username in the changelog.
• 8791fdb changelog: v1.21.1 draft
• 906367d kfake: regression test for share Record.Recycle + pool reuse
• dbba9ab kgo: deflake TestDirectPartitionPurge
• Additional commits viewable in compare view

Updates github.com/twmb/franz-go/pkg/kadm from 1.17.2 to 1.18.0

Changelog

Sourced from github.com/twmb/franz-go/pkg/kadm's changelog.

v1.18.0

This release adds support for Kafka 3.7, adds a few community requested APIs, some internal improvements, and fixes two bugs. One of the bugfixes is for a deadlock; it is recommended to bump to this release to ensure you do not run into the deadlock. The features in this release are relatively small.

This adds protocol support for KIP-890 and KIP-994, and adds further protocol support for [KIP-848][KIP-848]. If you are using transactions, you may see a new kerr.TransactionAbortable error, which signals that your ongoing transaction should be aborted and will not be successful if you try to commit it.

Lastly, there have been a few improvements to pkg/sr that are not mentioned in these changelog notes.

Bug fixes

• If you canceled the context used while producing while your client was at the maximum buffered records or bytes, it was possible to experience deadlocks. This has been fixed. See #832 for more details.

• Previously, if using GetConsumeTopics while regex consuming, the function would return all topics ever discovered. It now returns only the topics that are being consumed.

Improvements

• The client now internaly ignores OutOfOrderSequenceNumber errors that are encountered when consuming if possible. If a producer produces very infrequently, it is possible the broker forgets the producer by the next time the producer produces. In this case, the producer receives an OutOfOrderSequenceNumber error. The client now internally resets properly so that you do not see the error.

Features

• AllowRebalance and CloseAllowingRebalance have been added to GroupTransactSession.
• The FetchTopic type now has includes the topic's TopicID.
• The ErrGroupSession internal error field is now public, allowing you to test how you handle the internal error.
• You may now receive a kerr.TransactionAbortable error from many functions while using transactions.

Relevant commits

• 0fd1959d kgo: support Kafka 3.8's kip-890 modifications
• 68163c55 bugfix kgo: do not add all topics to internal tps map when regex consuming
• 3548d1f7 improvement kgo: ignore OOOSN where possible

... (truncated)

Commits

• 0a9996b Merge pull request #841 from twmb/1.18-changelog
• 835c682 CHANGELOG: note incoming release
• d771ddf Merge pull request #838 from twmb/810
• 04356d7 Merge pull request #835 from twmb/819
• 3d71b14 Merge pull request #834 from twmb/805
• 019799a Merge pull request #829 from andrewstucki/sr-client-opts
• 3a0f09a Merge pull request #814 from noamcohen97/new-offset-helper
• 6028e72 Merge pull request #794 from twmb/790
• 581d7ef Merge pull request #789 from sbuliarca/errgroupsession-export-err
• fd084a5 Merge pull request #760 from twmb/753
• Additional commits viewable in compare view

Updates github.com/twmb/franz-go/pkg/kmsg from 1.12.0 to 1.13.1

Changelog

Sourced from github.com/twmb/franz-go/pkg/kmsg's changelog.

v1.13.1

This patch release fixes a bug where a producer could enter a deadlock if a topic is deleted and recreated very quickly while producing.

• 769e02f producer: avoid deadlock when when quickly recreating a topic

v1.13.0

This release contains a few new APIs, two rare bug fixes, updates to plugins, and changes the library to now require 1.18.

Go version

This library has supported Go 1.15 since the beginning. There have been many useful features that this library has not been able to use because of continued backcompat for 1.15. There is really no reason to support such an old version of Go, and Go itself does not support releases prior to 1.18 -- and 1.18 is currently only supported for security backports. Switching to 1.18 allows this library to remove a few 1.15 / 1.16 backcompat files, and allows switching this library from interface{} to any.

Behavior changes

If group consuming fails with an error that looks non-retryable, the error is now injected into polling as a fake errored fetch. Multiple people have ran into problems where their group consumers were failing due to ACLs or due to network issues, and it is hard to detect these failures: you either have to pay close attention to logs, or you have to hook into HookGroupManageError. Now, the error is injected into polling.

Bug fixes

This release contains two bug fixes, one of which is very rare to encounter, and one of which is very easy to encounter but requires configuring the client in a way that (nearly) nobody does.

Rare: If you were using EndAndBeginTransaction, there was an internal race that could result in a deadlock.

Rare configuration: If you configured balancers manually, and you configured CooperativeSticky with any other eager balancer, then the client would internally sometimes think it was eager consuming, and sometimes think it was cooperative consuming. This would result in stuck partitions while consuming.

Features

... (truncated)

Commits

• 1a59c2d Merge pull request #404 from twmb/bugfix
• 5e0ba1c document incoming v1.13.1, update readme, fix golangci-lint
• d984c21 Merge pull request #401 from bgranvea/fix-segment-bench
• 769e02f producer: avoid deadlock when when quickly recreating a topic
• 5c2a90c set async commit
• 8cb298d Merge pull request #399 from twmb/dependabot/go_modules/examples/hooks_and_lo...
• 1141ce4 Merge pull request #397 from twmb/dependabot/go_modules/examples/hooks_and_lo...
• d5ef6e0 Merge pull request #398 from twmb/dependabot/go_modules/examples/bench/google...
• 8215a54 Merge pull request #400 from twmb/dependabot/go_modules/plugin/kprom/google.g...
• 6fdb469 build(deps): bump google.golang.org/protobuf in /plugin/kprom
• Additional commits viewable in compare view