Hi guys, Thanks a lot for your reply. As a first try I would like to avoid to manage IP addresses. I love Ignite multicast auto-discovery.
In a basic scenario it would be fine for me even if I could create a logically separated grids. I'm wondering if the API IgniteConfiguration#setGridName could be used for that or I will need to create explicitly a ClusterGroup <http://apacheignite.gridgain.org/v1.1/docs/cluster-groups>. Thanks, Paolo On Wed, Oct 14, 2015 at 1:28 PM, Alexey Kuznetsov <[email protected]> wrote: > Hi, Paolo. > > In addition to Ivan answer, I'd like to note that you could even start > several independent grids inside one JVM (sometimes could be useful for > debug from IDE). > See documentation: > https://apacheignite.readme.io/docs/cluster-config#static-ip-based-discovery > > On Wed, Oct 14, 2015 at 5:50 PM, Ivan Veselovsky < > [email protected]> wrote: > >> Hi, Paolo, >> please try to use >> org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder as >> the IpFinder in TcpDiscoverySpi. This is "IP Finder which works only with >> pre-configured list of IP addresses specified via {@link >> #setAddresses(Collection)} method." >> Also you may need to specify different >> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#setLocalPort ports to >> allow several server nodes on the same machine and better differentiate >> nodes of the 2 different topologies. >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/How-keep-separate-different-grid-instances-on-the-same-network-tp1609p1610.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
