You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2023/10/20 13:54:00 UTC
[jira] [Resolved] (IGNITE-20501) Calcite engine. Memory leak in MailboxRegistryImpl#remotes on JOINs
[ https://issues.apache.org/jira/browse/IGNITE-20501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov resolved IGNITE-20501.
----------------------------------------
Fix Version/s: 2.16
Release Note: SQL Calcite: Fixed memory leak in MailboxRegistryImpl#remotes
Resolution: Fixed
[~ivandasch], thanks for the review! Merged to master.
> Calcite engine. Memory leak in MailboxRegistryImpl#remotes on JOINs
> -------------------------------------------------------------------
>
> Key: IGNITE-20501
> URL: https://issues.apache.org/jira/browse/IGNITE-20501
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, ise
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When JOIN relational operator is executed, downstream of JOIN can be closed if only one side of JOIN is already drained (see last lines of {{MergeJoinNode.InnerJoin#join}}, for example). In this case query can be prematurely closed, and after this, message for another side of join can arrive and register new {{Inbox}} (see {{ExchangeServiceImpl#onMessage(UUID, QueryBatchMessage)}}), that never will be unregistered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)