Clustering is a feature where two or more instances running on the same or different machines can share the same repository view. Ideally, all cluster instances should have exactly the same content and request to any node in the cluster should return the same result.
Clustering in CQ provides the following benefits,
§ High Availability - Cluster helps to provide high availability in case either server break down or repository break down.
§ Improve Performance - Load can be balanced between a cluster node to improve performance.
§ Backup - Through clustering real-time backup is possible if one of the nodes is acting as a passive node.
In CQ each repository (Or instance) is referred to as a node. There is always one master in Cluster, Other Nodes are called as Slave. Slave and master communicate with each other over TCP/IP. If one instance comes down, other nodes take over as master and the whole cluster continue to work.
Clustering Architecture
CQ Cluster can be of two type
§ Active / Active Cluster - Where write is happening on all the nodes in the cluster.
This is ideal for load balancing
Active / Passive Cluster - Where write is not happening on one or more nodes. This is ideal for load balancing and backup.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.