Solace Cache Redundancy on a Single Event Broker
When deploying a Distributed Cache on a Solace event broker,Solace recommends that at least two Solace Cache Instances be deployed per Cache Cluster, each hosted on a separate server, as shown in the figure below. This deployment model ensures that no cached data is lost, and caching services to clients is not interrupted in the event that a host server fails.
In the case of a Distributed Cache with multiple Cache Clusters, Solace Cache Instances from different Cache Clusters can be hosted on the same server; for example, Cluster-1-Cache-Instance-1, Cluster-2-Cache-Instance-1, Cluster-3-Cache-Instance-1 could all be hosted on the same server to avoid hosting all Solace Cache Instances of a particular Cache Cluster on the same server.
In this configuration:
-
The Solace Cache Instances and the Cache Cluster must be configured to be part of the Distributed Cache.
-
We recommend enabling the
stop-on-lost-messageproperty for the Solace Cache Instances