I have a simpler scenario in mind: just one client connecting to the cluster of say 50 servers via ssh-tunnel.
I would be ready to define 50 tunnels forwarding to 50 servers on the cluster, but it does not seem supported?? Discovery works via a single tunnel, static-based discovery of the multicast-based cluster and AddressResolver, but TcpCommunicationSpi does not, as the discovery returns list of internal addresses of the cluster which are private of course, i.e. node from the list of nodes is defined as such: TcpDiscoveryNode [id=e8744d31-ce77-43d6-b3de-09dfa22516dc, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 192.168.168.22], sockAddrs=[0:0:0:0:0:0:0:1%lo:48500, /127.0.0.1:48500, /192.168.168.22:48500], discPort=48500, order=2, intOrder=2, lastExchangeTime=1475454891191, loc=false, ver=1.7.0#19700101-sha1:00000000, isClient=false] and 192.168.168.22 addrs is used. I would imagine that AddressResolver could be used for TcpCommunicationSpi that would translate both 192.168.168.22:COMMS_PORT into my localhost:SSH_TUNNELED_PORT_FOR_192.168.168.22. Is it possible? Am I missing something, the same problem would be with NATed/Firewalled addresses always, except the localhost the router/firewall address would be returned? Thanks Krzysztof -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels-tp273p8046.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
