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 2021/10/08 08:02:00 UTC
[jira] [Closed] (FLINK-24182) Tasks canceler should not immediately
interrupt
[ https://issues.apache.org/jira/browse/FLINK-24182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Nowojski closed FLINK-24182.
----------------------------------
Resolution: Fixed
Merged to master as 53592f88d4b..026675a5cb8 with keeping interruptions in clean cancelation
> Tasks canceler should not immediately interrupt
> -----------------------------------------------
>
> Key: FLINK-24182
> URL: https://issues.apache.org/jira/browse/FLINK-24182
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Reporter: Arvid Heise
> Assignee: Piotr Nowojski
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> While debugging resource leaks (FLINK-24131), I found that any connector is immediately interrupted on cancel. Hence, any attempts of using blocking calls in {{close}} to cleanup resources are immediately unreliable (e.g. aborting transactions).
> It would be nice if tasks get a grace period (e.g. task.cancellation.interval) where they can try to free resources in a proper, potentially blocking fashion before being interrupted.
> Nevertheless, connectors should always expect interruptions during shutdown, in particular when the user-configurable grace period is depleted. I'd add that to the connector documentation in a separate effort.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)