Hazelcast client & server version compatibility

[victo...@gmail.com]

If I have dedicated Hz nodes (forming a cluster) as server and use java native client (on client side), do the Hz versions have to be the same? Say if I have version 3.1.2 for both Hz nodes and native client now, but in the future I want to upgrade Hz nodes to 3.2. Will client and server still be compatible? I wanna understand Hz dev's plan/approach on this.  For practical deployment/operation, client and server versions should be able to advance separately (as long as gap is not big). Thanks!

[Peter Veentjer]

They will not be compatible.

In Hazelcast 3.2 a completely new client architecture has been introduced based on NIO. So afaik it will not be compatible.

Peter.

On Tue, Jan 21, 2014 at 9:20 AM, <victo...@gmail.com> wrote:

If I have dedicated Hz nodes (forming a cluster) as server and use java native client (on client side), do the Hz versions have to be the same? Say if I have version 3.1.2 for both Hz nodes and native client now, but in the future I want to upgrade Hz nodes to 3.2. Will client and server still be compatible? I wanna understand Hz dev's plan/approach on this.  For practical deployment/operation, client and server versions should be able to advance separately (as long as gap is not big). Thanks!

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at http://groups.google.com/group/hazelcast.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/651c5a71-9869-4c03-a97d-34af9e48a7da%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[victo...@gmail.com]

After 3.2, will you keep server and client jar version backward compatible?

I remember in your 2.X manual, native client is preferred over other ways to access data in server cache. Seems this won't work any more with what you said. Do you recommend using REST interface to access data in server cache? Then we will need to put a load balancer in front of Hz node cluster, in this case, what do you suggest as the way for the load balancer to detect which node is not healthy (so it won't send traffic to that node).

Thanks!