RE: slow node discovering on Kubernetes

[Alexandr Shapkin]

Hello Maxim,   Could you please share the current state of this issue? Have you managed to resolve it or it still exists?   What is your pods configuration in terms of resource usage?   From: Maxim Volkomorov Sent: Thursday, March 11, 2021 11:44 PM To: user@ignite.apache.org Subject: slow node discovering on Kubernetes   Hi Ignite team, We're running an Ignite cluster with 10 server nodes at Kubernetes. Using empty ignite configuration we can't run more than 5 nodes in a normal time. Trying to deploy 10 nodes on our empty config leads to weird discovery problems caused by "IgniteSpiException: Node with the same ID was found".    After increasing the AckTimeout=10000 and switching to G1GC, cluster was started, but time still long and getting TcpDiscoverySpi errors. I checked connections and port availability between nodes and found nothing suspicious. I've attached a log with one of 10 nodes deploying. Our ignite config is default-config.xml with only TcpDiscoveryKubernetesIpFinder. Would you like to take a look and give us some suggestions on how to reduce deploy time? Thanks, Maxim