Thanks, I meant Rolling Update of the same version of Ignite (2.16). Not upgrade to a new version. We have our ignite embedded in Spring Boot application, and when changing code we need to deploy new version of the jar.HumphreyOn 3 Sep 2024, at 19:24, Gianluca Bonetti wrote:HelloIf you want to up
Hello
If you want to upgrade Apache Ignite version, this is not supported by
Apache Ignite
"Ignite cluster cannot have nodes that run on different Ignite versions.
You need to stop the cluster and start it again on the new Ignite version."
https://ignite.apache.org/docs/latest/installation/upgrad
Hello, we have several pods with ignite caches running in kubernetes. We only
use memory mode (not persistence) and want to perform rolling update of without
losing data. What metric should we monitor to know when it’s safe to replace
the next pod?
We have tried the Cluser.Rebalanced (1) metric
