Move to @nest-native/kafka 0.6.0 - #127
Merged
Merged
Conversation
0.6.0's one change in default behavior is the retry backoff: a message whose failure maps to 'retry' now pauses its partition for 1 s, doubling up to 30 s, where 0.5.x redelivered it about every 0.5 s. The app keeps the default error mapper, which maps an unexpected error (a plain Error, such as a database outage inside a handler) to 'retry', so those redeliveries now back off instead of hitting the failing dependency twice a second per stuck partition. Handlers that reject bad input throw 4xx exceptions, which commit, as before. The live Kafka e2e's redelivery is a duplicate the inbox deduplicates, not a retry, so the backoff never engages there; the spec passes against Redpanda as before. The release also awaits async error mappers, stops committing records fetched during a graceful shutdown, and adds a health indicator, topic patterns and dead-letter helpers; none of the app's API use changes. @nest-native/messaging 0.7.0 already peers ^0.6.0, so the tree keeps one deduplicated copy. The README's compatibility row moves to 0.6.x (docs:check gates it).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Moves the app from
@nest-native/kafka^0.5.1 to ^0.6.0.@nest-native/messaging0.7.0 already peers^0.6.0, so the tree keeps a single deduplicated copy. The README's compatibility row moves to0.6.x;docs:checkgates it.The one behavior change the app picks up is the retry backoff. A message whose failure maps to
'retry'now pauses its partition for 1 s, doubling up to 30 s. On 0.5.x it came back about every 0.5 s, forever.Error, such as a database outage inside a handler, to'retry'. Those redeliveries now back off instead of hitting the failing dependency twice a second per stuck partition.TaskSummaryConsumerexplains why.'retry', so the backoff doesn't engage there. The spec passes against Redpanda in about 7 s, as before.The release's fixes also apply without code changes: async error mappers are awaited, and a graceful shutdown no longer commits records it fetched but didn't process. Its new health indicator, topic patterns and dead-letter helpers are opt-in and not used here.