[FLINK-22535] Resource leak would happen if exception thrown during AbstractInvokable#restore of task life

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.13.0
• Fix Version/s: 1.14.0, 1.13.1
• Component/s: Runtime / Task
• Labels: pull-request-available
• Assignee: Anton Kalashnikov
• Reporter: Yun Tang
• Created: 29/Apr/21 14:49
• Updated: 28/May/21 11:08
• Resolved: 03/May/21 13:22

Description

FLINK-17012 introduced new initialization phase such as AbstractInvokable.restore, however, if invokable.restore() throws exception out, no more StreamTask#cleanUpInvoke would be called, leading to resource leak.

We internally leveraged another way to use managed memory by registering specific operator identifier in memory manager, forgetting to call the stream task cleanup would let stream operator not be disposed and we have to face critical resource leak.

Issue Links

• is caused by: FLINK-17012 Expose stage of task initialization
• links to: GitHub Pull Request #15820