Good point. In some cases I use near cache. Maybe for the ones that don't need it, I can use the thin client.
I'm looking to see what port and I.Ps are made available to the container and see if I can set up address forwarding or whatever it's called. On Fri, 26 Jun 2020 at 11:35, Stephen Darlington < [email protected]> wrote: > Yes, thick client nodes are peers, and so can both accept and initiate > connections to and from other nodes. > > It’s often easier to get a thin-client to work under these circumstances, > as they behave in a more traditional client-server manner. Is that a viable > option? > > Regards, > Stephen > > On 26 Jun 2020, at 16:28, John Smith <[email protected]> wrote: > > Hi, I have 3 server nodes deployed on VMs as far as they are concerned > it's practically bare metal installation. > > My client nodes CLIENT=TRUE connect from within DC/OS Cluster using docker > in either bridged network or closed DC/OS network. I.e: They are not > visible to the network. > > In TCP/IP Discovery this seems to work no problem, client connects and I > can do cache operations no problem. > > But does the server node ever attempt to connect back to the client node > in any way? > And do the clients need some kind special address resolution / port > forwarding? > > I see there's a BasicAddressResolver class, but it's not really documented > in the official docs. > > > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/BasicAddressResolver.html > > > >
