ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-4154) Optimize amount of data stored in discovery history
Date Mon, 31 Oct 2016 12:30:58 GMT
Semen Boikov created IGNITE-4154:
------------------------------------

             Summary: Optimize amount of data stored in discovery history
                 Key: IGNITE-4154
                 URL: https://issues.apache.org/jira/browse/IGNITE-4154
             Project: Ignite
          Issue Type: Task
          Components: general
            Reporter: Semen Boikov
            Assignee: Semen Boikov
             Fix For: 1.8


Currently on large clusters with lots of caches amount of data stored in tcp discovery history
can grow too much.

What can be improved:
- TcpDiscoveryNodeAddedMessage.oldNodesDiscoData contains per-node discovery data. For cache
component essentially this is list of configured caches, and for joined node at the time when
'collectDiscoveryData' is called this list should be the same on all nodes, so it can be stored
once instead of per-node map
- even after message is discarded it is still stored in PendingMessages collection, looks
like it can be safely removed after discarding
- now system property IGNITE_DISCOVERY_HISTORY_SIZE controls both size of events needed for
client reconnects and number of topology snapshots stored in GridDiscoveryManager, need have
two properies
- for clients TcpDiscoveryNodeAddFinishedMessage.clientDiscoData can be initialized only when
message is sent to joining client 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message