Re: Issues with Clients joining cluster on Kubernetes (EKS)

Hi aes, I don't know any issues related to Kubernetes which appeared in 2.7. As Evgenii mentioned it seems there are some issues on the server node. There is no message in 2 hours in server logs. Most likely this is related to the environment (not Ignite). Do you observe any issues with connectiv

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Interestingly, when I downgraded from 2.7 -> 2.6 the connection from the client became much more stable. is this a known regression in 2.7? Something that will be addressed in a 2.7.X or 2.8 release? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Yes I followed this guide to get started, and I have egress/ingress rules that allow intra-cluster communication on every port that I have verified. If discovery and communication ports werent open, I feel like the client would have a hard time connecting after the timeout elapsed, wouldnt it? -

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Yes, I know that users have deployments in kubernetes and they don't have any issues with that. Did you follow this instruction: https://apacheignite.readme.io/docs/kubernetes-deployment ? Please make sure that ports for Discovery and Communication are open in this environment. Evgenii пт, 3 мая

Re: Issues with Clients joining cluster on Kubernetes (EKS)

I didnt deploy the client right away, got distracted :) From your experience is ignite on kubernetes something thats considered to be stable? If so, I feel like there are some settings I must be missing. Between something blocking the discovery thread, or the client timing out on every first attemp

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Why there is no lines in the server log between these two: [17:10:48,827][INFO][sys-#149][GridCachePartitionExchangeManager] Sending Full Message for AffinityTopologyVersion [topVer=10, minorTopVer=1] performed in 1 ms. [19:39:58,910][INFO][disco-event-worker-#62][GridDiscoveryManager] Added new n

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Sure, set preferIPv4 on the client, and set IGNITE_QUIET to false. logs attached. Thank you!! serverLogs.serverLogs clientLogs.clientLogs

Re: Issues with Clients joining cluster on Kubernetes (EKS)

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.s

Issues with Clients joining cluster on Kubernetes (EKS)

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 cl