[ 
https://issues.apache.org/jira/browse/FLINK-24530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-24530:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> GlobalCommitter might not commit all records on drain
> -----------------------------------------------------
>
>                 Key: FLINK-24530
>                 URL: https://issues.apache.org/jira/browse/FLINK-24530
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataStream, Connectors / Common
>    Affects Versions: 1.14.0, 1.13.2, 1.15.0
>            Reporter: Fabian Paul
>            Assignee: Arvid Heise
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>
> If a pipeline has a unified Sink that implements a {{Committer}} and 
> {{GlobalCommitter}} committables are forwarded from the {{Committer}} on 
> either receiving {{notifyCheckpointCompleted}} or {{endInput}}. 
> Since both methods are triggered by RPC calls we currently do not guarantee 
> an order when either method is called on the {{Committer}} or 
> {{GlobalCommitter}}. This can lead to that the {{GlobalCommitter}} receives 
> the RPC call at first and tries to commit although the {{Committer}} has 
> nothing forwarded yet. For the normal streaming execution, it means that the 
> visibility of the final commit could be delayed by one checkpoint.
> Unfortunately, if the pipeline is stopped with a savepoint and drained the 
> {{endInput}} might be called at the {{GlobalCommitter}} before the 
> {{Committer}} leading to potential data loss.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to