Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 27 Jun 2017 08:18:00 +0000 (UTC)
From: "Alexey Goncharuk (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.13082742.1498551471000.113070.1498551480077@Atlassian.JIRA>
In-Reply-To: <JIRA.13082742.1498551471000@Atlassian.JIRA>
References: <JIRA.13082742.1498551471000@Atlassian.JIRA> <JIRA.13082742.1498551471185@jira-lw-us.apache.org>
Subject: [jira] [Created] (IGNITE-5593) Affinity change message leak on
 massive topology updates
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 27 Jun 2017 08:18:04 -0000

Alexey Goncharuk created IGNITE-5593:
----------------------------------------

             Summary: Affinity change message leak on massive topology updates
                 Key: IGNITE-5593
                 URL: https://issues.apache.org/jira/browse/IGNITE-5593
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 1.7
            Reporter: Alexey Goncharuk
            Priority: Critical
             Fix For: 2.1


When late affinity assignment is enabled, we complete the exchange future with custom discovery event. Since discovery topology events usually are much faster than exchange futures completion, it is possible that a newly joined node can 'see' the affinity change messages that are related to previous topology versions when this node even was not present in the topology.

When this message is received, an exchange future is created and this message is added to discoEvts list. However, this future never completes on this node because init() is never called. This means that this exchange future sits in the exchange set with the affinity change message.

Since the number of topology changes (and, thus, messages) can be quite large, this leads to excessive memory consumption on the starting node. I've observed ~3Gb of heap wasted on one of the nodes when > 200 nodes were restarted.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)