There are cases where you would need to synchronize multiple clusters. Synchronization of clusters is named as WAN (Wide Area Network) Replication because it is mainly used for replicating different clusters running on WAN. Imagine having different clusters in New York, London and Tokyo. Each cluster would be operating at very high speed in their LAN (Local Area Network) settings but you would want some or all parts of the data in these clusters replicating to each other. So updates in Tokyo cluster goes to London and NY, in the meantime updates in New York cluster is synchronized to Tokyo and London.
You can setup active-passive WAN Replication where only one active node replicating its updates on the passive one. You can also setup active-active replication where each cluster is actively updating and replication to the other cluster(s).
In the active-active replication setup, there might be cases where each node is updating the same entry in the same named distributed map. Thus, conflicts will occur when merging. For those cases, conflict-resolution will be needed. Here is how you can setup WAN Replication for London cluster for instance:
<hazelcast> <wan-replication name="my-wan-cluster"> <target-cluster group-name="tokyo" group-password="tokyo-pass"> <replication-impl>com.hazelcast.impl.wan.WanNoDelayReplication</replication-impl> <end-points> <address>10.2.1.1:5701</address> <address>10.2.1.2:5701</address> </end-points> </target-cluster> <target-cluster group-name="london" group-password="london-pass"> <replication-impl>com.hazelcast.impl.wan.WanNoDelayReplication</replication-impl> <end-points> <address>10.3.5.1:5701</address> <address>10.3.5.2:5701</address> </end-points> </target-cluster> </wan-replication> <network> ... </network> </network> ... </hazelcast>
This can be the configuration of the cluster running in NY, replicating to Tokyo and London. Tokyo and London clusters should have similar configurations if they are also active replicas.
If NY and London cluster configurations contain
Tokyo cluster doesn't then it means NY and London are active endpoints and Tokyo is passive endpoint.
As noted earlier you can have Hazelcast replicate some or all of the data in your clusters. You might have
5 different distributed maps but you might want only one of these maps replicating across clusters.
So you mark which maps to replicate by adding
element into map configuration.
<hazelcast> <wan-replication name="my-wan-cluster"> ... </wan-replication> <network> ... </network> <map name="my-shared-map"> ... <wan-replication-ref name="my-wan-cluster"> <merge-policy>hz.PASS_THROUGH</merge-policy> </wan-replication-ref> </map> </network> ... </hazelcast>
Here we have
is configured to replicate itself to the cluster targets defined
Note that you will also need to define a
for merging replica entries and resolving conflicts
during the merge. Default merge policy is
which will apply all in-coming updates as is.