[jira] [Updated] (FLINK-25695) TemporalJoin cause state leak in some cases

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-25695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-25695:
-----------------------------------
    Labels: pull-request-available stale-major  (was: pull-request-available)

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 Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> TemporalJoin cause state leak in some cases
> -------------------------------------------
>
>                 Key: FLINK-25695
>                 URL: https://issues.apache.org/jira/browse/FLINK-25695
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Runtime
>    Affects Versions: 1.14.3
>            Reporter: Lyn Zhang
>            Priority: Major
>              Labels: pull-request-available, stale-major
>         Attachments: image-2022-01-29-11-11-11-705.png, image-2022-01-29-11-11-27-550.png, image-2022-01-29-11-11-31-967.png, image-2022-01-29-11-12-43-016.png, test.sql
>
>
> Last year, I reported the similar bug of TemporalJoin cause state leak. Detail: FLINK-21833
> Recently, I found the fix code can reduce the the leak size but can not resolve it completely.
> The code of line 213 cause it and the right fix is to invoke cleanUp() method.
> In FLINK-21833, we discussed when the code is running on line 213, that means Left State, Right State, registeredTimerState is empty, actually the Left State and Right State value(MapState) is empty but the key is still be in state, So invoke state.clear() is necessary. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)