Chapter 2. Adding a node to an existing cluster


Synchronize the server clocks using NTP
Create a certificate for a new cluster node
Starting the server on a new node
Connect to the existing cluster, and define the new node's connection parameters

The previous chapter walks through the process of creating a new object repository, with a single node. An object repository with only one node is not very much fun. Things get interesting when multiple nodes, multiple servers, form a single object repository. The process is the same whether adding the repository's second, or the tenth node.

The process of adding a node to an existing object repository cluster consists of the following steps. The examples in this chapter use the same test environment as in Chapter 1, Setting up a new cluster (with one, initial, node), the cluster certificates are installed on the machine called octopus, which also runs one of its nodes (its initial node). This chapter walks through the process of adding a new node named monster. Both nodes run on machines that have the same name, and stasher is installed on both machines:

Synchronize the server clocks using NTP

stasher requires that all nodes have synchronized system clocks. Before configuring a new node, make sure that all existing and potential nodes in the cluster have their system clock synchronized using NTP.