ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 11:45:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clustering: improve tutorial, revise related API methods

Browse Source
This commit is contained in:
mDuo13
2018-09-13 15:32:32 -07:00
parent 891def5003
commit 582717de76
5 changed files with 87 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
content/concepts/the-rippled-server/clustering.md
View File

@@ -8,19 +8,7 @@ If you are running multiple `rippled` servers in a single datacenter, you can co
If you are running a validator as a [private peer](peer-protocol.html#private-peers), Ripple recommends using a cluster of `rippled` servers as proxy servers.
## Configuring Clustering
To enable clustering, change the following sections of your [config file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) for each server:
1. 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 = peer` setting in their `rippled.cfg`. Example:
[ips_fixed]
192.168.0.1 51235
192.168.0.2 51235
2. Generate a unique seed (using the [validation_create method][]) for each of your servers, and configure it under the `[node_seed]` section. The `rippled` server uses this key to sign its messages to other servers in the peer-to-peer network.
3. 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.
For a tutorial on how to set up your servers in a cluster, see [Cluster `rippled` Servers](cluster-rippled-servers.html).
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}