Scaling up the cluster
We created a cluster to house all the data with a number of nodes holding both the owned partitions and backups. However, what happens if we need to scale? This can be for a number of reasons. For example, approaching the current overall memory capacity of the application is rather demanding and can saturate a hardware resource. The solution in both cases is simple—add more nodes.
So, if we were to start with a cluster of four nodes that hold approximately 4 million objects, each individual node will hold roughly 1 million owned objects (and 1 million backups). When we introduce a new node, Hazelcast reacts by assigning partitions from the existing nodes to it. This will cause the existing data to stream across to the new ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access