A NULL coordinator shouldn't be fatal #4020
Merged
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
if an failed FindCoordinatorRequest sets txn coordinator to NULL just after it reconnects.
aa8a036
to
6c6e108
Compare
6c6e108
to
5099f4f
Compare
edenhill
suggested changes
Oct 18, 2022
the fatal error rd_kafka_idemp_pid_fsm: Assertion `rk->rk_eos.txn_curr_coord' failed
5099f4f
to
b8b5864
Compare
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.
When a PID epoch bump is requested and the producer is waiting
to reconnect to the transaction coordinator, a failure in a find coordinator
request could cause txn_curr_coord to be set to NULL and an assert to fail.
This was fixed by retrying when the coordinator is known.