Hazelcast removed CP Subsystem from Community edition

vert-x3 / vertx-hazelcast

Hazelcast Cluster Manager for Vert.x

Apache License 2.0

77 stars 76 forks source link

Hazelcast removed CP Subsystem from Community edition #194

Closed JSchering closed 3 months ago

JSchering commented 3 months ago

Hazelcast has removed the CP subsystem from the community edition in 5.4 and above. Will vert.x continue to have hazelcast as an option for the cluster manager with this removal? Support was removed in 5.4 and now only the paid platform version will have the CP subsystem which controls operations like distributed locking, synchronization, distributed maps and leader election. How will this impact vert.x use of hazelcast?

JSchering commented 3 months ago

Sorry for adding a question here, All links I've found for vert.x community or questions don't appear to work or have little to no activity

tsegismont commented 3 months ago

No problem @JSchering

We are aware of this and working with Hazelcast folks on a solution for Hazelcast community users (without the CP subsystem).

Vert.x 4 works HZ 5.3 (see https://vertx.io/blog/eclipse-vert-x-4-5-8/#default-hazelcast-version)

HZ 5.4 will be supported in Vert.x 5 only, I think.

JSchering commented 3 months ago

@tsegismont can you clarify if this means in vert.x 5 you must use hazelcast platform (paid) version or are you working on a way around the limitations in the community edition of hazelcast?

tsegismont commented 3 months ago

I meant that we're working with Hazelcast folks on having a solution in Vert.x 5 for both community users and enterprise customers. The community users won't be able to use the CP subsystem (this mainly affects counter and locks semantics) so there will be a workaround using maps.

vietj commented 3 months ago

@JSchering overall we will use the most up to date community version of Hazelcast that can make the clustering work

frant-hartm commented 3 months ago

Few clarifications:

CP subsystem is being removed from the Hazelcast open-source edition in the upcoming 5.5.0 release, not 5.4.0 (already released) This PR https://github.com/vert-x3/vertx-hazelcast/pull/197 reimplements Lock and Counter using an IMap (which stays available in Hazelcast open-source edition). This doesn't provide as strong guarantees as the solution based on the CP subsystem, but the guarantees are roughly the same as in https://vertx.io/docs/vertx-hazelcast/java/#_using_an_existing_hazelcast_cluster where the CP subsystem is configured with 0 cp member count (= unsafe mode). Vert.x users can continue using Hazelcast Cluster Manager with the open source edition of Hazelcast.
Hazelcast will provide another module that will use different implementation of the lock / counter based on CP subsystem, if you are a Hazelcast customer, you will be able to use this together with Hazelcast Enterprise edition.

tsegismont commented 3 months ago

Thanks for the clarifications @frant-hartm