Hello! Have you also tried setting IgniteConfiguration.localHost property?
Regards, -- Ilya Kasnacheev чт, 22 окт. 2020 г. в 20:54, Gilles <[email protected]>: > Hello, > > I'm currently moving a project from development stage to production. The > aim is that my cluster server nodes are running on multiple virtual private > servers, inside a VPN (10.0.0.0/24). > > But how do I make sure that I lock any communication of a node to either a > specific network interface, or a static virtual IP (eg 10.0.0.3)? > > Some googling got me to this answer from old documentation. > > <property name="communicationSpi"> > <bean > class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> > <property name="localAddress" value="10.0.0.3"/> > </bean> > </property> > > However the nodes are still accessible on their public IP addresses. So > the question is, what is the correct way to isolate them from the public? > > I will be using a software firewall on these servers too, but I like to > have the peace of mind from the extra layer of security. > > > Thanks in advance, > Gilles > > And to the creators, maintainers and contributors, thank you so much for > this great piece of software! Never had so much fun doing "cumbersome" > database work. > > > >
