Hello all, I recently started using Ignite for benchmarking a research project on a local multi-node cluster. Now I need to deploy the cluster on geographically distributed nodes, but I am stuck at setting up the connection on EC2 machines.
I have closely followed the TCP-based discovery instructions with static IPs of EC2 nodes. The first node seems to be starting up perfectly fine, but when I launch the second node, even though it triggers a topology change in the first node, it is immediately bounced back to the single-node (initial) state (I'll attach a sample output of the node 1 at the end of the message). I have used S3 Based Discovery method as well, but the problem persists. I appreciate your time and sorry for asking a novice question Bests, Kia [14:28:07] Ignite node started OK (id=431973b5) [14:28:07] Topology snapshot [ver=1, servers=1, clients=0, CPUs=2, offheap=0.77GB, heap=1.0GB] [14:28:07] ^-- Node [...] [14:28:07] Data Regions Configured: [14:28:07] ... [14:29:40] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4, offheap=1.5GB, heap=2.0GB] [14:29:40] ^-- Node [...] [14:29:40] Data Regions Configured: [14:29:40] ... [14:29:40] Topology snapshot [ver=3, servers=1, clients=0, CPUs=2, offheap=0.77GB, heap=1.0GB] [14:29:40] ... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
