From 3d4647cabe32b167eb65494960ab7b9ee95fada2 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Tue, 23 Sep 2025 11:55:20 -0700 Subject: [PATCH] Reword shard_db removal notice --- docs/infrastructure/installation/capacity-planning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/infrastructure/installation/capacity-planning.md b/docs/infrastructure/installation/capacity-planning.md index a893d823ff..aa3944099c 100644 --- a/docs/infrastructure/installation/capacity-planning.md +++ b/docs/infrastructure/installation/capacity-planning.md @@ -157,7 +157,7 @@ The `[database_path]` configures separate bookkeeping databases: these include t As a general rule, you can safely delete the database files (both the ledger store and the bookkeeping databases) for a `rippled` server when it isn't running; this clears any stored ledger history the server has, but it can re-acquire that data from the network. However, if you delete the `wallet.db` file in the `[database_path]`, you must manually reapply runtime configuration changes such as [amendment votes](../configuration/configure-amendment-voting.md) and [peer reservations](../configuration/peering/use-a-peer-reservation.md). -If your server has a `[shard_db]` stanza, you can remove it. History Sharding was removed in `rippled` version 2.3.0, so this config stanza no longer does anything. +If your config file has a `[shard_db]` stanza, you can safely remove it. This section is obsolete and has no effect. {% badge href="https://github.com/XRPLF/rippled/releases/tag/2.3.0" %}Removed in: rippled 2.3.0{% /badge %} ##### Amazon Web Services