You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vadim Pakhnushev (Jira)" <ji...@apache.org> on 2025/08/20 10:20:00 UTC

[jira] [Created] (IGNITE-26251) Event sink memory leak

Vadim Pakhnushev created IGNITE-26251:
-----------------------------------------

             Summary: 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


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)