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-10199: Accept only one task per exception in queue for failed tasks #15849

Merged
merged 1 commit into from
May 3, 2024

Conversation

cadonna
Copy link
Contributor

@cadonna cadonna commented May 2, 2024

Currently, the state updater writes multiple tasks per exception in the output queue for failed tasks. To add the functionality to remove tasks synchronously from the state updater, it is simpler that each element of the output queue for failed tasks holds one single task.

This commit refactors the class that holds exceptions and failed tasks in the state updater -- i.e., ExceptionAndTasks -- to just hold one single task.

Committer Checklist (excluded from commit message)

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

…led tasks

Currently, the state updater writes multiple tasks per exception in the output
queue for failed tasks. To add the functionality to remove tasks synchronously
from the state updater, it is simpler that each element of the output queue for
failed tasks holds one single task.

This commit refactors the class that holds exceptions and failed tasks
in the state updater -- i.e., ExceptionAndTasks -- to just hold one single
task.
@cadonna cadonna requested a review from lucasbru May 2, 2024 19:12
Copy link
Member

@lucasbru lucasbru left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

Yes, storing a nested collection here added unnecessary complexity

Copy link
Member

@lucasbru lucasbru left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

Yes, storing a nested collection here added unnecessary complexity

@cadonna
Copy link
Contributor Author

cadonna commented May 3, 2024

Failures are unrelated!

@cadonna cadonna merged commit 240243b into apache:trunk May 3, 2024
1 check failed
gongxuanzhang pushed a commit to gongxuanzhang/kafka that referenced this pull request Jun 12, 2024
…led tasks (apache#15849)

Currently, the state updater writes multiple tasks per exception in the output
queue for failed tasks. To add the functionality to remove tasks synchronously
from the state updater, it is simpler that each element of the output queue for
failed tasks holds one single task.

This commit refactors the class that holds exceptions and failed tasks
in the state updater -- i.e., ExceptionAndTasks -- to just hold one single
task.

Reviewers: Lucas Brutschy <lbrutschy@confluent.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants