Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3035
I think we can take a very simple approach here. Many other parts of the
code follow the approach to tolerate exceptions thrown during cancellation, or
during asynchronous calls on closed operators.
- The client may be closed during shutting down of the Kafka08Fetcher,
before even the surrounding KafkaConsumerBase knows that it is closing
- The KafkaConsumerBase tries to commit offsets, sees the exception, and
re-throws it since it assumes it.
- We can make the Kafka08Fetcher catch exceptions when committing
offsets, and only re-throwing them if the fetcher is still running. That should
do the trick.
BTW: There are plans to make the streaming API sources appear to be single
threaded, to avoid that sources have to plan for such situations.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
