Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
To: dev@ignite.apache.org
From: =?UTF-8?B?5p2O546J54+PQDE2Mw==?= <18624049226@163.com>
Subject: about isolated ignite clusters on the same set of machines
Message-ID: <8b306455-ad2c-f6dc-8faa-bae8a0e49e99@163.com>
Date: Tue, 20 Sep 2016 21:52:08 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=gbk; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Tue, 20 Sep 2016 13:52:21 -0000

Guys:

in our network, we want to isolate some of the machine to build cluster 
for testing, I looked at the following document,also do the test, but 
found that this document may not be correct:

https://apacheignite.readme.io/v1.7/docs/cluster-config#isolated-ignite-clusters-on-the-same-set-of-machin

If the addresses property of TcpDiscoveryVmIpFinder is set to 127.0.0.1, 
multiple ignite nodes started in the same machine,is the isolation of 
cluster, has nothing to do with the localPort attribute, if do not set 
the addresses property, even if the localPort property of 
TcpDiscoverySpi and TcpCommunicationSpi are diff, also belong to the 
same cluster.


The way I think is to set the IP address list for the addresses 
property, but it doesn't look elegant, does anyone in the community know 
the right, or elegant way?