fix(deps): update module github.com/twmb/franz-go/pkg/kadm to v1.17.1 #43738
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.17.0->v1.17.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
twmb/franz-go (github.com/twmb/franz-go/pkg/kadm)
v1.17.1Compare Source
===
This patch release fixes four bugs (two are fixed in one commit), contains two
internal improvements, and adds two other minor changes.
Bug fixes
If you were using the
MaxBufferedBytesoption and ever hit the max, odds arelikely that you would experience a deadlock eventually. That has been fixed.
If you ever produced a record with no topic field and without using
DefaultProduceTopic,or if you produced a transactional record while not in a transaction, AND if the client
was at the maximum buffered records, odds are you would eventually deadlock.
This has been fixed.
It was previously not possible to set lz4 compression levels.
There was a data race on a boolean field if a produce request was being
written at the same time a metadata update happened, and if the metadata
update has an error on the topic or partition that is actively being written.
Note that the race was unlikely and if you experienced it, you would have noticed
an OutOfOrderSequenceNumber error. See this comment
for more details.
Improvements
Canceling the context you pass to
Producenow propagates in two more areas:the initial
InitProducerIDrequest that occurs the first time you produce,and if the client is internally backing off due to a produce request failure.
Note that there is no guarantee on which context is used for cancelation if
you produce many records, and the client does not allow canceling if it is
currently unsafe to do so. However, this does mean that if your cluster is
somewhat down such that
InitProducerIDis failing on your new client, youcan now actually cause the
Produceto quit. See this commentfor what it means for a record to be "safe" to fail.
The client now ignores aborted records while consuming only if you have
configured
FetchIsolationLevel(ReadCommitted()). Previously, the client reliedentirely on the
FetchResponseAbortedTransactionsfield, but it's possiblethat brokers could send aborted transactions even when not using read committed.
Specifically, this was a behavior difference in Redpanda, and the KIP that introduced
transactions and all relevant documents do not mention what the broker behavior
actually should be here. Redpanda itself was also changed to not send aborted
transactions when using read committed, but we may as well improve franz-go as well.
Decompression now better reuses buffers under the hood, reducing allocations.
Brokers that return preferred replicas to fetch from now causes an info level
log in the client.
Relevant commits
305d8dckgo: allow record ctx cancelation to propagate a bit more24fbb0fbugfix kgo: fix deadlock in Produce when using MaxBufferedBytes1827addbugfix kgo sink: fix read/write race for recBatch.canFailFromLoadErrsd7ea2c3bugfix fix setting lz4 compression levels (thanks @asg0451!)5809decoptimise: use byteBuffer pool in decompression (thanks @kalbhor!)cda897dkgo: add log for preferred replicase62b402improvement kgo sink: do not back off on certain edge case9e32bf9kgo: ignore aborted txns if usingREAD_UNCOMMITTEDConfiguration
📅 Schedule: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.