Hello! In my experience, on EC2 nodes usually use internal network to talk to each other. They will advertise these to any nodes trying to connect, which will cause issues.
Is it an option for you to use some flavor of Thin Client to talk to your cluster? We do not recommend having heterogenous, non-collocated clusters, and this includes thick client nodes. Regards, -- Ilya Kasnacheev пт, 9 авг. 2019 г. в 03:35, sri hari kali charan Tummala < [email protected]>: > Hi All, > > I am trying to connect a ignite ec2 instance (one node) remotely from > local PC Mac Intellij Idea I am using TcpDicoverySpi to connect ignite ec2 > instance public IP but its failing to connect I did open all the ports I > was able to do ssh and ping the host from my local PC even on the remote > host I am able to access internet, ignite right now fails with below error. > > [20:14:54] Failed to connect to any address from IP finder (will retry to > join topology every 2000 ms; change 'reconnectDelay' to configure the > frequency of retries): [/52.204.222.254:47500, /52.204.222.254:47501, / > 52.204.222.254:47502, /52.204.222.254:47503, /52.204.222.254:47504, / > 52.204.222.254:47505, /52.204.222.254:47506, /52.204.222.254:47507, / > 52.204.222.254:47508, /52.204.222.254:47509, /52.204.222.254:47510] > > I am following below blog , can any one help how to access ignite cluster > which is setup remotely do I need to build my code and run in the cluster > by ssh to the box ? > > > https://aws.amazon.com/blogs/big-data/real-time-in-memory-oltp-and-analytics-with-apache-ignite-on-aws/ > > 4.222.254:47507, /52.204.222.254:47508, /52.204.222.254:47509, / > 52.204.222.254:47510] > > [image: Thumbnail] > <https://uploads.disquscdn.com/images/23e365052ba57ed2be6399b06c036ada661bc92584046760584c85afefe4a4e4.png> > > > -- > Thanks & Regards > Sri Tummala > >
