You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Daradur (JIRA)" <ji...@apache.org> on 2016/12/27 14:01:01 UTC
[jira] [Created] (IGNITE-4501) Improvement of connection in a
cluster of new node
Vyacheslav Daradur created IGNITE-4501:
------------------------------------------
Summary: Improvement of connection in a cluster of new node
Key: IGNITE-4501
URL: https://issues.apache.org/jira/browse/IGNITE-4501
Project: Ignite
Issue Type: Improvement
Reporter: Vyacheslav Daradur
h3. Main description:
Cluster nodes connect a ring.
For example: we have 6 nodes: A, B, C, D, E, F.
They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, etc.
If some node leaves topology, adjacent nodes must reconnect.
If nodes A, B, C are in same physical place, nodes D, E, F are in other place, and places lost connect each other, we will have many ways of reconnections.
At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then we have only one reconnect (C
will be connected to A or F will be connected to D -- depends on what part of the cluster was alive.
Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where n -- number of nodes).
h3. Approach:
It is necessary to develop approach of node insertion to the correct place for creation of the correct ring-topology.
h3. Solutions:
Main idea is a sorting according to latency.
* group nodes in arcs on an ARC_ID. (manualy?)
* implement NodeComparator (nodes on the same host : nodes on the same subnet : other nodes). We will use it when we connect a new node.
* [dev list thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=Ke83-5-Rh9g@mail.gmail.com%3E]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)