[
https://issues.apache.org/jira/browse/IGNITE-20501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777787#comment-17777787
]
Ignite TC Bot commented on IGNITE-20501:
----------------------------------------
{panel:title=Branch: [pull/10996/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 TIMEOUT , Out Of
Memory Error , Exit Code , TC_SERVICE_MESSAGE
|https://ci2.ignite.apache.org/viewLog.html?buildId=7564837]]
{panel}
{panel:title=Branch: [pull/10996/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7374580]]
* {color:#013220}IgniteCalciteTestSuite:
JoinRehashIntegrationTest.testResourceCleanup - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7374658&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> 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)
