[
https://issues.apache.org/jira/browse/FLINK-28386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dong Lin updated FLINK-28386:
-
Description: 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 tasks have reached
end-of-data. (was: 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 tasks have received
end-of-data.)
> Trigger an immediate checkpoint after all tasks has reached end-of-data
> ---
>
> Key: FLINK-28386
> URL: https://issues.apache.org/jira/browse/FLINK-28386
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Checkpointing
>Reporter: Yun Gao
>Assignee: Jiang Xin
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> 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 tasks have reached end-of-data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
