chia7712 commented on PR #16686:
URL: https://github.com/apache/kafka/pull/16686#issuecomment-2413455632
> Then, if you try to close the consumer or to unsubscribe to cleanly leave
the group, the old consumer works because there are no interrupt checks on
those paths whereas the new one fails short because calling get() (e.g. on a
future) will thrown an interrupt exception again. This is where the difference
is.
Yes, that’s the side effect when we delegate all tasks to the background
thread and then block on wait—making many async consumer APIs interruptible.
Do we have a rulebook on how consumer APIs should handle interruptions if
we’re aiming to align behavior? If not, maybe we need to draw these first. In
this PR, we’re juggling two different interruption issues:
1. Interruptions can disrupt the execution of listeners, close,
and unsubscribe.
2. Interruptions aren’t being propagated to the listener or
background thread.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
