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

add warning about removed feature

Browse Source
This commit is contained in:
Oliver Eggert
2025-02-07 16:54:32 -08:00
parent ce7868fdf7
commit d3b86a014c
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/infrastructure/configuration/data-retention/history-sharding.md
View File

@@ -8,8 +8,7 @@ labels:
- Core Server - Core Server
--- ---
# History Sharding # History Sharding
{% admonition type="danger" name="Warning" %}History sharding was removed in [rippled 2.3.0](https://github.com/XRPLF/rippled/releases/tag/2.3.0). This page describes historical behavior of older versions of XRP Ledger software.{% /admonition %}
{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.90.0" %}Introduced in: rippled 0.90.0{% /badge %}
As XRP Ledger servers run, they naturally produce a database containing data about the ledgers they built or acquired during network runtime. Each server stores that ledger data in its _ledger store_, but [online deletion](online-deletion.md) removes old ledgers' data automatically over time. History sharding provides a separate storage system for older ledger history so that the network can divide up the work of recording the entire (multiple terabyte) history of the XRP Ledger. As XRP Ledger servers run, they naturally produce a database containing data about the ledgers they built or acquired during network runtime. Each server stores that ledger data in its _ledger store_, but [online deletion](online-deletion.md) removes old ledgers' data automatically over time. History sharding provides a separate storage system for older ledger history so that the network can divide up the work of recording the entire (multiple terabyte) history of the XRP Ledger.