Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Hazelcast migration section #48

Merged
merged 1 commit into from
Dec 8, 2020
Merged

Add Hazelcast migration section #48

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions asciidoc/chapters/assembly_mg_changes-in-clustering.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ This section explains the changes in clustering.

include::../modules/con_mg_clustered_flag_removed_from_option_classes.adoc[leveloffset=+1]

include::../community_features/hazelcast.adoc[leveloffset=+1]

include::../modules/con_mg_changes-in-infinispan-cluster-manager.adoc[leveloffset=+1]

include::../community_features/ignite.adoc[leveloffset=+1]
Expand Down
22 changes: 22 additions & 0 deletions asciidoc/community_features/hazelcast.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
[id="changes-in-hazelcast-cluster-manager_{context}"]
= Changes in Hazelcast cluster manager

The following section describes the changes in the Hazelcast cluster manager.

== Updates in custom configurations

The Hazelcast cluster manager is based on Hazelcast 4.

In {VertX} {v4}, the clustering SPI has been redesigned. The subscription data model has changed. As a result of this, {VertX} {v3x} nodes and {VertX} {v4} nodes cannot be added together in the same Hazelcast cluster.

The {VertX} applications are not impacted by this change as the EventBus and SharedData APIs remain the same.

If you had a custom Hazelcast configuration file in your {VertX} {v3x} application:

* Add the map `__vertx.nodeInfo`.

----
<map name="__vertx.nodeInfo">
<backup-count>1</backup-count>
</map>
----