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-16699: Have Streams treat InvalidPidMappingException like a ProducerFencedException #15919

Merged

Conversation

wcarlson5
Copy link
Contributor

KStreams is able to handle the ProducerFenced (among other errors) cleanly. It does this by closing the task dirty and triggering a rebalance amongst the worker threads to rejoin the group. The producer is also recreated. Due to how streams works (writing to and reading from various topics), the application is able to figure out the last thing the fenced producer completed and continue from there. InvalidPidMappingException should be treated the same way.

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

@wcarlson5 wcarlson5 requested a review from mjsax May 10, 2024 17:18
Copy link
Contributor

@ableegoldman ableegoldman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

100% agree -- I came to the same conclusion when discussing this exception here

Guess I'll have to update the last paragraph after we ship this!

@wcarlson5
Copy link
Contributor Author

There were no new or related test failures.

@wcarlson5 wcarlson5 merged commit 57d30d3 into apache:trunk May 14, 2024
1 check failed
@mjsax mjsax added the streams label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants