[
https://issues.apache.org/jira/browse/IGNITE-26251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev resolved IGNITE-26251.
---------------------------------------
Resolution: Fixed
https://github.com/apache/ignite-3/commit/00a2189d8379b8ed8a41cb6868f20dc56b4eee4a
> Event sink memory leak
> ----------------------
>
> Key: IGNITE-26251
> URL: https://issues.apache.org/jira/browse/IGNITE-26251
> Project: Ignite
> Issue Type: Bug
> Reporter: Vadim Pakhnushev
> Assignee: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When cluster configuration listener is invoked in the
> {{ConfigurationBasedSinkRegistry}} with the same sink configuration, old
> sinks are not stopped leading to possible memory leaks, for example, in the
> {{WebhookSink}} there's a forever running executor with a task that captures
> {{this}} and, in turn, {{clusterIdSupplier}} which is actually {{IgniteImpl}}
> instance.
> The solution is to stop old sinks regardless of whether they are present in
> the new configuration or not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
