[
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 stale-minor (was:
auto-deprioritized-major)
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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
