Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KAFKA-18660: Transactions Version 2 doesn't handle epoch overflow correctly #18758

Merged
merged 1 commit into from
Jan 31, 2025

Conversation

jolshan
Copy link
Member

@jolshan jolshan commented Jan 30, 2025

Pick to 4.0
Fixed the typo that used the wrong producer ID and epoch when returning so that we handle epoch overflow correctly.

We also had to rearrange the concurrent transaction handling so that we don't self-fence when we start the new transaction with the new producer ID.

I also tested this with a modified version of the code where epoch overflow happens on the first epoch bump (every request has a new producer id)

Reviewers: Artem Livshits [email protected], Jeff Kim [email protected]

Conflicts due to #18639 not being merged in 4.0 -- no functional differences.

…rectly (apache#18730)

Fixed the typo that used the wrong producer ID and epoch when returning so that we handle epoch overflow correctly.

We also had to rearrange the concurrent transaction handling so that we don't self-fence when we start the new transaction with the new producer ID.

I also tested this with a modified version of the code where epoch overflow happens on the first epoch bump (every request has a new producer id)

Reviewers: Artem Livshits <[email protected]>, Jeff Kim <[email protected]>
@jolshan jolshan merged commit 685ce7b into apache:4.0 Jan 31, 2025
8 checks passed
airlock-confluentinc bot pushed a commit to confluentinc/kafka that referenced this pull request Feb 3, 2025
…rectly (apache#18730) (apache#18758)

Fixed the typo that used the wrong producer ID and epoch when returning so that we handle epoch overflow correctly.

We also had to rearrange the concurrent transaction handling so that we don't self-fence when we start the new transaction with the new producer ID.

I also tested this with a modified version of the code where epoch overflow happens on the first epoch bump (every request has a new producer id)

Reviewers: Artem Livshits <[email protected]>, Jeff Kim <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants