CORE-20892: use a unique producer transactional id when creating producers #6390
Conversation
This file contains 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
…ucers. This ensures producers recreated will not overlap with older producers that have transactions timed out on the kafka broker
LWogan
requested review from
jasonbyrner3,
ronanbrowne,
rick-r3,
simon-johnson-r3,
blsemo,
Omar-awad,
aditisdesai,
vinir3,
vkolomeyko,
Sakpal,
owenstanford,
davidcurrie and
conalsmith-r3
as code owners
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 ensures producers recreated will not overlap with older producers that have transactions timed out on the kafka broker. The brokers keep track of in flight transaction. Sometimes they can become stuck in an unhealthy state. When the producer is recreated, if it uses the same transaction.id config value for the client, the broker will expect the producer complete the previous transaction