[
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 stale-major (was:
auto-deprioritized-critical)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-deprioritized-critical, stale-major
>
> 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.3.4#803005)
