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

Flink Jira Bot commented on FLINK-13695:
----------------------------------------

This critical issue is unassigned and itself and all of its Sub-Tasks have not 
been updated for 7 days. So, it has been labeled "stale-critical". If this 
ticket is indeed critical, please either assign yourself or give an update. 
Afterwards, please remove the label. 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: Critical
>              Labels: stale-critical
>
> 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)

Reply via email to