Re: Local Client not connecting to Server deployed in azure cloud.

Hello! Then there's an obvious problem than something is trying to join with your node. I expect it's the node itself, due to network configuration it doesn't realise that it phones to itself. -- Ilya Kasnacheev 2018-05-10 20:51 GMT+03:00 JP : > I am just running only

Re: Local Client not connecting to Server deployed in azure cloud.

I am just running only one node. I didn't run other nodes... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! If your client tries to connect to your server and server sees this as traffic from 168.63.129.16, unfortunately that won't work. Intra-cluster Ignite connections can be reversed (it is not a client-server protocol rather than server-server), this means that connections should come from

Re: Local Client not connecting to Server deployed in azure cloud.

Please check this https://blogs.msdn.microsoft.com/mast/2015/05/18/what-is-the-ip-address-168-63-129-16/ That ip belongs to Azure -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local Client not connecting to Server deployed in azure cloud.

I can see a suspicious "Failed to read magic header (too few bytes received)" message. Something is not right. Can we see log for the node that tries to connect here? Is it possible, btw, that 10.0.0.4 and 168.63.129.16 are on the same server and thus it tries to discover itself without

Re: Local Client not connecting to Server deployed in azure cloud.

Hi, Please find the logs from this link https://files.fm/u/mprbmab3#/view/logs.txt -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! Unfortunately it's hard to say from this message alone, can you put logs from all nodes somewhere? However, immediate red sign is that local and remote are in different class of networks. Regards, Ilya -- Ilya Kasnacheev 2018-05-10 19:45 GMT+03:00 JP : > Now, I

Re: Local Client not connecting to Server deployed in azure cloud.

Now, I am just running only one server. In that only I am facing this error 2018-05-10 16:42:31 INFO TcpDiscoverySpi:475 - Started serving remote node connection [rmtAddr=/168.63.129.16:64338, rmtPort=64338] 2018-05-10 16:42:32 ERROR TcpCommunicationSpi:495 - Failed to process selector key

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! Are you sure that you can connect from one server to another? Maybe you have to adjust firewall rules? What does "nc anotherhost:47500" return? Can you type something there, get a response from server? Regards, -- Ilya Kasnacheev 2018-05-10 19:26 GMT+03:00 JP :

Re: Local Client not connecting to Server deployed in azure cloud.

Just noticed that three ipaddress assigned to server vm. Change my configuration with communication api. Still facing issue. 2018-05-10 16:12:33 ERROR TcpDiscoverySpi:495 - Failed to initialize connection (this can

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! I'm not sure about that. I recommend removing the guesswork from this scenario, trying to configure everything explicitly. Once you get your cluster working you can ease some options to default. Regards, -- Ilya Kasnacheev 2018-05-10 18:04 GMT+03:00 JP : > what I

Re: Local Client not connecting to Server deployed in azure cloud.

what I thought is, if we are not setting communication api it will take default value as local only. Is that the scenario right? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local Client not connecting to Server deployed in azure cloud.

As I have already said, try to add TcpCommunicationSpi setter and set local address for it. Taking hints from https://apacheignite.readme.io/docs/cluster-config#section-isolated-ignite-clusters-on-same-set-of-machines Regards, -- Ilya Kasnacheev 2018-05-10 17:31 GMT+03:00 JP

Re: Local Client not connecting to Server deployed in azure cloud.

This is my Ignite Configurations for both server in vm1 and client in vm2, public static IgniteConfiguration getIgniteConfig() throws Throwable { TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi(); discoverySpi.setLocalPort(47500);

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! Can you please provide details on the exact network configuration on both servers? BTW, if the remoteAddr in your example was an external IP, this might be the source of problem. Try setting localAddress on communicationSpi to local address of server on both clients and server nodes.

Re: Local Client not connecting to Server deployed in azure cloud.

Hi, Now I have two VM in azure cloud. In one vm started Ignite Server and in another Ignite Clients. Both are configured with same subnet. Server and Client are connected. But below error throwing continuously.. Can you give some suggestions to solve this issue?. 2018-05-10 13:45:45 ERROR

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! I can see that your local node is trying to connect to private IP ranges: 10.0.0.9 and 192.168.1.31 Those are probably valid only in limited context (just on the cloud, or just in your private network) and not valid otherwise. You could

Re: Local Client not connecting to Server deployed in azure cloud.

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

Re: Local Client not connecting to Server deployed in azure cloud.

Hi, Please check that 47101 port is accessible and try to run with argument -Djava.net.preferIPv4Stack=true Thanks, Pavel 2018-05-09 5:55 GMT+03:00 JP : > Hi, >I have running ignite servers and clusters running in Azure cloud West > US > region. > > I am trying to

Local Client not connecting to Server deployed in azure cloud.

Hi, I have running ignite servers and clusters running in Azure cloud West US region. I am trying to connect my local ignite(South India) to server. Initially both are connections, but after few seconds client automatically disconnected. Show these error messages: 2018-05-09 08:21:56 WARN