If you are running multiple
rippled servers in a single datacenter, you can configure those servers into a cluster to maximize efficiency. Running your
rippled servers in a cluster provides the following benefits:
rippledservers share the work of cryptography. If one server has verified the authenticity of a message, the other servers in the cluster trust it and do not re-verify.
- Clustered servers share information about peers and API clients that are misbehaving or abusing the network. This makes it harder to attack all servers of the cluster at once.
- Clustered servers always propagate transactions throughout the cluster, even if the transaction does not meet the current load-based transaction fee on some of them.
If you are running a validator as a private peer, Ripple recommends using a cluster of
rippled servers as proxy servers.
To enable clustering, change the following sections of your config file for each server:
List the IP address and port of each other server under the
[ips_fixed]section. The port should be the one from the other servers'
protocol = peersetting in their
[ips_fixed] 192.168.0.1 51235 192.168.0.2 51235
Generate a unique seed (using the validation_create method) for each of your servers, and configure it under the
rippledserver uses this key to sign its messages to other servers in the peer-to-peer network.
Add each node's peer-communication public key (generated in step 2) to the
[cluster_nodes]section of each of your other servers' config files.