[jira] [Commented] (FLINK-28386) Trigger an immediate checkpoint after all sources finished

["Piotr Nowojski (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-28386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714956#comment-17714956 ] 

Piotr Nowojski commented on FLINK-28386:
----------------------------------------

[~zlzhang0122] Checkpoint could be used just to make the side effects visible (committing results in two phase commit operators/sinks). On the other hand, why savepoint makes any sense? There is no point in recovering  from such snapshot anyway.

About the ticket. Taking into account unaligned checkpoints, I think a better condition would be to trigger a checkpoint once all tasks are finished. With unaligned checkpoints, downstream tasks can be still processing in-flight data, while upstream sources are finished, so triggering checkpoint on finished sources wouldn't achieve the desired goal of stopping the job faster.

> Trigger an immediate checkpoint after all sources finished
> ----------------------------------------------------------
>
>                 Key: FLINK-28386
>                 URL: https://issues.apache.org/jira/browse/FLINK-28386
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Checkpointing
>            Reporter: Yun Gao
>            Priority: Major
>
> Currently for bounded job in streaming mode, by default it will wait for one more checkpoint to commit the last piece of data. If the checkpoint period is long, the waiting time might also be long. to optimize this situation, we could eagerly trigger a checkpoint after all sources are finished. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)