[
https://issues.apache.org/jira/browse/FLINK-13695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13695:
-----------------------------------
Labels: auto-deprioritized-critical auto-deprioritized-major
auto-deprioritized-minor (was: auto-deprioritized-critical
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Integrate checkpoint notifications into StreamTask's lifecycle
> --------------------------------------------------------------
>
> Key: FLINK-13695
> URL: https://issues.apache.org/jira/browse/FLINK-13695
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Not a Priority
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-deprioritized-minor
>
> The {{StreamTask's}} asynchronous checkpoint notifications are decoupled from
> the {{StreamTask's}} lifecycle. Consequently, it can happen that a
> {{StreamTask}} is terminating/cancelling and still sends asynchronous
> checkpoint notifications (e.g. acknowledge/decline checkpoint notifications).
> This is problematic because a cancelling/terminating {{StreamTask}} might
> cause an asynchronous checkpoint to fail which is expected and should not be
> reported to the {{JobMaster}}.
> Hence, the checkpoint notifications should be coupled with the
> {{StreamTask's}} lifecycle (e.g. notifications must be sent from the
> {{StreamTask's}} main thread) and if not valid, then they need to be filtered
> out/suppressed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
