[
https://issues.apache.org/jira/browse/IGNITE-20501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-20501:
--------------------------------------
Labels: calcite ignite ise (was: calcite calcite3-required ignite ise)
> 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, ignite, 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)
