You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2020/12/09 12:42:00 UTC
[jira] [Commented] (FLINK-20548) Provide an option to disable
propagation of timed out barriers
[ https://issues.apache.org/jira/browse/FLINK-20548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246501#comment-17246501 ]
Piotr Nowojski commented on FLINK-20548:
----------------------------------------
I don’t like the behaviour of changing UC to AC, as it would add complexity to the system, without clear benefit to me. Or maybe there is some rare use case which would benefit from such change, but all the other uses cases would suffer (more complexity, more complicated code, more moving parts, more things to document and understand). After all, if someone wants to limit the amount of persisted data, he can just increase the timeout value.
Also if the motivation is to limit persisted data, a better and I think more useful idea would be to add size limit for in-flight data before triggering unaligned checkpoint. It would let users to control the amount of persisted data much more strictly.
> Provide an option to disable propagation of timed out barriers
> --------------------------------------------------------------
>
> Key: FLINK-20548
> URL: https://issues.apache.org/jira/browse/FLINK-20548
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing, Runtime / Configuration, Runtime / Web Frontend
> Reporter: Roman Khachatryan
> Priority: Major
>
> A follow-up ticket after FLINK-19681 to address issues not directly related to checkpointing (see [discussion|https://github.com/apache/flink/pull/13827#discussion_r527794600]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)