[
https://issues.apache.org/jira/browse/FLINK-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5738:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
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.
> Destroy created backend when task is canceled
> ---------------------------------------------
>
> Key: FLINK-5738
> URL: https://issues.apache.org/jira/browse/FLINK-5738
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
> Affects Versions: 1.2.0
> Reporter: Xiaogang Shi
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> When a task is canceled, the {{ClosableRegistry}} will be closed in the
> cancel thread. However, the task may still in the creation of
> {{KeyedStateBackend}}, and it will fail to register the backend to the
> {{ClosableRegistry}}. Because the backend is not assigned to the operator yet
> (due to the exception), the backend will not be destroyed when the task
> thread exits.
> A simple solution is to catch exception in the registering and destroy the
> created backend in the case of failures.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
