[
https://issues.apache.org/jira/browse/FLINK-25920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729290#comment-17729290
]
Hector Rios commented on FLINK-25920:
-------------------------------------
Hello all.
To add more context to this issue, I was working with a customer who was
experiencing this error. I found the content in the following issue really
helpful.
https://issues.apache.org/jira/browse/FLINK-30238
In the specific case of this customer, the issue was being caused by including
--drain on their call to stop-with-savepoint. I was able to recreate the issue
using a very simple job reading from a Kafka source and sinking back to Kafka.
Unfortunately, it was not consistent across versions. I was able to reproduce
it on 1.15.3 but not on 1.15.4. Granted, it was a quick test, and I wanted to
do a more thorough test to reproduce the issue consistently.
One interesting wrinkle on this one is that it occurs in 1.15.x, but the same
job deployed into 1.14.x does not produce the issue.
Thanks.
> Allow receiving updates of CommittableSummary
> ---------------------------------------------
>
> Key: FLINK-25920
> URL: https://issues.apache.org/jira/browse/FLINK-25920
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataStream, Connectors / Common
> Affects Versions: 1.15.0, 1.16.0
> Reporter: Fabian Paul
> Priority: Major
>
> In the case of unaligned checkpoints, it might happen that the checkpoint
> barrier overtakes the records and an empty committable summary is emitted
> that needs to be correct at a later point when the records arrive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
