Hi Maxim, Not really, I haven’t used flannel plugin and I’m not quite sure about network recommendations as well. Well, besides something basic, like avoid stretching between multiple availability zones and some persistence tuning, Like disabling MMAP for WAL (IGNITE_WAL_MMAP=false) > The problem still actual, we deployed same 10 nodes on google kubernetes and >got a normal time. Do you mean, that switching on GKE makes it working or it was the initial setup and nothing has changed since that? > For now we did not define any limits or requests, our ignite is the only deployment on the kubernetes. I was wondering cause if I remember correctly there might be some issues if your pods have insufficient resources, but unfortunately, no direct numbers. Well, default GKE instances should works ok on a default cluster, anyway. > Do you have any idea how to estimate network or hardware performance to find >possible bottlenecks? I think enabling DEBUG logs for discovery might help to see what’s really happening to the grid. <category name="org.apache.ignite.spi.discovery"> Btw, is it a persistent cluster or pure in-memory one? From: mvolkomorov Hello, Alexandr! The problem still actual, we deployed same 10 nodes on google kubernetes and got a normal time. For now we did not define any limits or requests, our ignite is the only deployment on the kubernetes. We use flannel network plugin (host-gw), are there any recommendations for the network plugin? Do you have any idea how to estimate network or hardware performance to find possible bottlenecks? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/ |
- RE: slow node discovering on Kubernetes Alexandr Shapkin
- RE: slow node discovering on Kubernetes mvolkomorov
- RE: slow node discovering on Kubernetes Alexandr Shapkin
- RE: slow node discovering on Kubernetes mvolkomorov
