From 8d0b44db5f21be30c1ce6149c51a835648c25bec Mon Sep 17 00:00:00 2001 From: Jess Heron Date: Fri, 2 Feb 2018 15:04:28 -0800 Subject: [PATCH] Removes a couple more 'nodes' --- content/concept-history-sharding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concept-history-sharding.md b/content/concept-history-sharding.md index 79439b8d00..ec18412a34 100644 --- a/content/concept-history-sharding.md +++ b/content/concept-history-sharding.md @@ -38,7 +38,7 @@ max_size_gb=50 **Tip:** Ripple recommends using NuDB for the shard store (`type=NuDB`). NuDB uses fewer file handles per shard than RocksDB. RocksDB uses memory that scales with the size of data it stores, which may require excessive memory overhead. -**Tip:** While both validator and tracking (or stock) `rippled` servers can be configured to use history shard stores, Ripple recommends adding history sharding only for non-validator nodes to reduce overhead for validator nodes. If you run a validator and want to manage ledger history using sharding, run a separate `rippled` server with sharding enabled. +**Tip:** While both validator and tracking (or stock) `rippled` servers can be configured to use history shard stores, Ripple recommends adding history sharding only for non-validator `rippled` servers to reduce overhead for validators. If you run a validator and want to manage ledger history using sharding, run a separate `rippled` server with sharding enabled. For more information, reference the `[shard_db]` example in the [rippled.cfg configuration example](https://github.com/ripple/rippled/blob/master/doc/rippled-example.cfg).