Online deletion edits per review

- Cleaned up can_delete method fields, errors
- Changed commands to delete old db files in full history tutorial
- Clarified RocksDB w/ rotational disks
- Clarified how many ledgers may be stored w/ online deletion
This commit is contained in:
mDuo13
2019-01-14 15:43:46 -08:00
parent 4669665aba
commit 9d88381c89
4 changed files with 19 additions and 15 deletions

View File

@@ -59,9 +59,9 @@ To configure your server to acquire and store full history, complete the followi
After disabling online deletion, the server ignores any data that was downloaded while online deletion was enabled, so you may as well clear up the disk space. For example:
rm -r /var/lib/rippled/db/rocksdb/*
rm /var/lib/rippled/db/*.db
rm /var/lib/rippled/db/*.sqlite
rm -r /var/lib/rippled/db/*
**Warning:** Be sure that you have not put any files you want to keep in the folder before you delete it. It is generally safe to delete all of a `rippled` server's database files, but you should only do this if the configured database folder is not used for anything other than `rippled`'s databases.
0. Start the `rippled` server, importing the database dump if you have one available:

View File

@@ -53,7 +53,9 @@ The example `rippled-example.cfg` file has the `type` field in the `[node_db]` s
#### More About Using RocksDB
[RocksDB](https://rocksdb.org/docs/getting-started.html) is an embeddable persistent key-value store that works well with both rotational disks and solid state disks.
[RocksDB](https://rocksdb.org/docs/getting-started.html) is an embeddable persistent key-value store.
RocksDB works well on solid-state disks. RocksDB performs better than NuDB when used with rotational disks, but you may still encounter performance problems unless you use solid-state disks.
RocksDB requires approximately one-third less [disk storage](#disk-space) than NuDB and provides better I/O latency. However, the better I/O latency comes as result of the large amount of RAM RocksDB requires to store data indexes.