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 tutorial edits per @ryangyoung review

Browse Source
This commit is contained in:
mDuo13
2018-10-04 11:31:57 -07:00
parent 582717de76
commit bbe36941e2
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/tutorials/manage-the-rippled-server/cluster-rippled-servers.md
View File

@@ -25,7 +25,7 @@ If you run multiple `rippled` servers in the same data center, you can configure
3. On each server, edit the [config file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg), modifying the following sections: 3. On each server, edit the [config file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg), modifying the following sections:
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` (usually 51235). Each member of the cluster should list all _other_ members of the cluster here. For example: 1. In the `[ips_fixed]` section, list the IP address and port of each _other_ member of the cluster. For each of those servers, the port number should match the `protocol = peer` port (usually 51235) from that server's `rippled.cfg`. For example:
[ips_fixed] [ips_fixed]
192.168.0.1 51235 192.168.0.1 51235
@@ -33,16 +33,14 @@ If you run multiple `rippled` servers in the same data center, you can configure
This defines specific peer servers to which this server should always attempt to maintain a direct peer-to-peer connection. This defines specific peer servers to which this server should always attempt to maintain a direct peer-to-peer connection.
2. Set the server's node seed one of the `validation_seed` values you generated using the [validation_create method][] in step 2. Each server must use a unique node seed. For example: 2. In the `[node_seed]` section, set the server's node seed to one of the `validation_seed` values you generated using the [validation_create method][] in step 2. Each server must use a unique node seed. For example:
[node_seed] [node_seed]
ssZkdwURFMBXenJPbrpE14b6noJSu ssZkdwURFMBXenJPbrpE14b6noJSu
This defines the key pair the server uses to sign peer-to-peer communications, excluding validation messages. This defines the key pair the server uses to sign peer-to-peer communications, excluding validation messages.
3. Set the members of the server's cluster, identified by their `validation_public_key` values. Each server should list the public keys of all _other_ members of the cluster here. Optionally, add a custom name for each server. 3. In the `[cluster_nodes]` section, set the members of the server's cluster, identified by their `validation_public_key` values. Each server should list the public keys of all _other_ members of the cluster here. Optionally, add a custom name for each server. For example:
For example:
[cluster_nodes] [cluster_nodes]
n9McNsnzzXQPbg96PEUrrQ6z3wrvgtU4M7c97tncMpSoDzaQvPar keynes n9McNsnzzXQPbg96PEUrrQ6z3wrvgtU4M7c97tncMpSoDzaQvPar keynes