Hi Josephine! Make sure, that TcpDiscoveryVmIpFinder has address of the local node on the list. Otherwise the first node won't be able to start, because discovery SPI won't find any nodes.
Also note, that TcpDiscoverySpi has localAddress and localPort properties. Try setting them according to your public IP and port. Refer to this page for more information: https://apacheignite.readme.io/docs/cluster-config Denis вт, 21 нояб. 2017 г. в 15:11, Josephine Barboza <[email protected] >: > Hi, > > > > I have setup ignite instances on two different VMs and I’m trying to > create a cluster using Static IP discovery using TcpDiscoveryVmIpFinder. > > I have a couple of questions: > > 1. Do I need to give loopback address or public IP for the node to > start before trying to connect to the other node in the cluster? What is > the recommended configuration for production? > 2. When I give loopback address/private IP it works(node starts before > trying the connect to other node) but when I give the public IP it does > not. Both the ports for discoverySpi and commSpi are open on the public IP > and I have used address resolver as well to map the private IP to the > public IP. Is there any other configuration required? > 3. Facing the same issue as mentioned in point 2 while connecting to > the node on the second VM where in spite of using address resolver the node > is unable to join the topology. > > > > Thanks. > > > > IMPORTANT NOTICE: This email and any files transmitted with it are > confidential and intended solely for the use of the individual or entity to > whom they are addressed. If you have received this email in error, please > notify the system manager and/or the sender immediately. >
