Hi, I see this warning in the logs:
Local node's value of 'java.net.preferIPv4Stack' system property differs from remote node's (all nodes in topology should have identical value) [locPreferIpV4=true, rmtPreferIpV4=null, locId8=20c2dc57, rmtId8=699d2d8c, rmtAddrs=[ignite-jwp-0.ignite.ignite-jwp.svc.cluster.local/10.100.78.98, / 127.0.0.1], rmtNode=ClusterNode [id=699d2d8c-a54b-4104-9f97-62d550352315, order=1, addr=[10.100.78.98, 127.0.0.1], daemon=false]] so, probably it makes sense to set java.net.preferIPv4Stack property to true on all the nodes in the cluster. Also, it would be great to check INFO logs from server nodes, please add -DIGNITE_QUIET=false property. Evgenii ср, 1 мая 2019 г. в 00:42, Aaron Stockton <[email protected]>: > I currently am running a 10 node Ignite cluster on EKS. I tried running it > was a k8s deployment, but the thrash in getting all the nodes to join and > agree on a topology was pretty painful, so its running currently as a > statefulset. > > Currently, the issue I am seeing is that when I try to deploy a client > node via kubernetes, the client node joins the cluster immediately, then > fails to gossip thus dropping it from the cluster. After some timeout the > node re-joins the cluster and is more or less stable from that point > forward. I'm looking for advice on configuring the client so that it can > join reliably. > > I'll attach logs from the client, server, and the relevant client config. > > Thanks in advance! > -aes >
