Cluster Architecture
The Terracotta cluster can be viewed topologically as a collection of clients communicating with a Terracotta Server Array.
The server array can be broken down into one or more logically independent stripes.
A stripe can be broken down into one or more servers. Each stripe contains a single active server and zero or more passive servers.
For more information on clients, active servers and passive servers, see the sections
Clients in a Cluster and
Active and Passive Servers.
There are multiple cluster types:
Cluster type | |
Single-server cluster | This is a cluster which consists of only one stripe, which internally contains only one server. This server is always the active server. |
High-availability cluster | This refers to a cluster where every stripe consists of at least two servers. This means that in addition to the active server there will be at least one passive server. This means that the stripe will continue in the event of server failure (as long as at least one server in the stripe stays available). Note that stripes do not share passive servers, so each stripe will need at least one passive to possess high-availability. |
Multi-stripe cluster | Multi-stripe refers to a cluster which consists of multiple independent stripes. For a multi-stripe cluster to possess high-availability, each stripe must consist of more than one server. |
Client perspective
Each client is logically independent of other clients. It sees the cluster as a collection of one or more stripes. It connects to the active server of each stripe in order to issue messages to the cluster.
Stripe perspective
Each stripe is logically independent of other stripes. It only concerns itself with the servers within it and the clients connected to it.
Specifically, the active server is the key point in each stripe: each stripe has exactly one active server and it is this server which interacts directly with each connected client and each passive server within the same stripe.
Contact Support
|
Community
|
Feedback