Ripple online deletion-优快云博客

本文详细介绍了如何在Ripple的rippled配置文件中设置online_delete参数，以优化存储空间使用。通过实例展示了在500GB存储环境下，合理配置分类账历史记录和在线删除策略的重要性。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Ripple online deletion

https://xrpl.org/configure-online-deletion.html

在您rippled的配置文件中，编辑节的online_delete字段[node_db]。


[node_db]
# Other settings unchanged ...
online_delete=2000
advisory_delete=0

设置online_delete为运行在线删除后要保留的最小分类帐版本数。如果使用自动删除（默认设置），
则服务器通常会在累积了这么多分类账版本两倍左右时运行删除。

complete_ledgers使用server_info方法定期检查服务器的范围，以确认要删除分类帐。

运行在线删除后，该complete_ledgers范围反映出较旧的分类帐不再可用。
随着服务器累积历史记录，可用的分类帐总数应缓慢增加到online_delete您配置的值的两倍，然后在运行在线删除时减少。

We have an instance with 500G storage.
We have explicitly configured the instance to prune transactions per this configuration:

[ledger_history]
324000

[node_db]
type=NuDB
path=/var/nvm/ripple-db/nudb
online_delete=324000
advisory_delete=0
In the first few month when we actively monitor the instance, we saw storage at one month is lower than the previous month:

2019/7/28:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1    436G  209G  206G  51% /var/nvm/ripple-db
2019/8/15:

2019/8/15:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1    436G  168G  246G  41% /var/nvm/ripple-db
But 4 months later, on 2019/12/5, rippled has now eaten all the storage:

But 4 months later, on 2019/12/5, rippled has now eaten all the storage:


$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1    436G  413G  506M 100% /var/nvm/ripple-db

参考：https://github.com/ripple/rippled/issues/3177