GridGain Enterprise and Ultimate editions provide Ignite compatible implementations with limited support for nodes with two concurrent versions to coexist temporarily in a cluster topology. This feature is called "Rolling Upgrade" and is only available in commercial GridGain versions. Please read the documentation carefully to evaluate whether this addresses your particular needs. Even in the GridGain commercial versions, this does not intend to enable running different versions of thick clients and server nodes in the same cluster under load.
https://www.gridgain.com/docs/latest/installation-guide/rolling-upgrades For Ignite, I would recommend operating duplicate clusters in a blue-green architecture, and thick clients should be managed as part of the cluster infrastructure. You should think of Thick Client nodes more like server nodes. They join the cluster as peers to servers, but in "client mode" they do not participate in data region or persistence. Manage them as a single pool per cluster, thick clients and servers together. Shut everything down on the blue cluster once the green cluster has been upgraded and all the tests pass, and cut over to green. Then in the next upgrade/release cycle shut down green when the blue cluster is fully upgraded and tests are all passing, and cut over to blue. On Tue, Oct 29, 2024 at 9:01 AM John Smith <java.dev....@gmail.com> wrote: > And this is specifically an open source vs "enterprise" feature? > > On Tue, Oct 29, 2024 at 2:33 AM Pavel Tupitsyn <ptupit...@apache.org> > wrote: > >> Yes, thick clients will fail to connect on version mismatch (thin clients >> will work across versions). >> >> On Mon, Oct 28, 2024 at 3:51 PM John Smith <java.dev....@gmail.com> >> wrote: >> >>> Are we limited by version when updating ignite? I have a 3 node >>> "central" cluster and a bunch of THICK clients connecting. Can we update >>> the central cluster to a newer version or will all the clients fail to >>> connect because of version mismatch? >>> >>
