Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3035
I this case, the exception would not be logged, true.
It is a very rare corner case that should not affect correctness, and not
really distinguishable from the case where an exception is thrown after the
source went into finishing mode.
My feeling is to not log here.
- The advantage is that we don't pollute the log with meaningless
exception in the common case (many users would be led onto a false track).
- Given that the corner case you described does not affect any expected
behavior (the committing action might as well not have happened at all it it
were started a few msecs later) it is okay to "swallow" the exception.
- If it does in fact affect the offset committing in more cases, it will
surely also occur at another committing attempt during execution.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
