ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Subject Re: Local Client not connecting to Server deployed in azure cloud.
Date Thu, 10 May 2018 13:10:09 GMT
Hello!

I can see that your local node is trying to connect to private IP ranges:
10.0.0.9 <http://10.0.0.9:47101> and 192.168.1.31 <http://192.168.1.31:0>

Those are probably valid only in limited context (just on the cloud, or
just in your private network) and not valid otherwise.

You could make sure that both your local node and server nodes exist on
public IP addresses. But it will be unfeasible and also a security disaster.

Or you could have a tunnel (let's say VPN) from your local network to your
cloud. Make sure that e.g. 10.x.x.x addresses are routed through that
tunnel and nothing else. I think that's the preferred course of action for
such case.

Or, if you can, you could make use of some thin clients.

Regards,

-- 
Ilya Kasnacheev

2018-05-10 15:17 GMT+03:00 JP <jopandy679@gmail.com>:

> Hi,
>    I am running ignite with -Djava.net.preferIPv4Stack=true and also ports
> 47100, 47101, 47500.
>
>    Server nodes and Client nodes are connecting but after some interval it
> throwing connection timeout.
> and in visior, if queried for cache -scan  then going to hang and after
> some
> time throwing failure detection issue.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Mime
View raw message