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

Update content/tutorials/manage-the-rippled-server/configuration/run-rippled-in-reporting-mode.md

Browse Source 
Co-authored-by: Rome Reginelli <mduo13@gmail.com>
This commit is contained in:
Amarantha Kulkarni
2022-01-18 11:38:40 -08:00
committed by Amarantha Kulkarni
parent b9ae479b6b
commit 68ab81b692
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/tutorials/manage-the-rippled-server/configuration/run-rippled-in-reporting-mode.md
View File

@@ -295,7 +295,7 @@ There are initiatives in progress to provide packages for reporting mode.
The answer depends on the location of your primary datastore. If you use Cassandra as the primary datastore, the disk space requirement to run rippled in reporting mode will be lower as the data is not stored on your local disk. The PostgreSQL server can be remote as well. The answer depends on the location of your primary datastore. If you use Cassandra as the primary datastore, the disk space requirement to run rippled in reporting mode will be lower as the data is not stored on your local disk. The PostgreSQL server can be remote as well.
Lastly, the p2p mode server only needs to keep very recent history, since reporting mode will persist long term history. Lastly, the P2P mode server only needs to keep very recent history, while the reporting mode server keeps long term history.
For more information on system requirements to run rippled, see https://xrpl.org/system-requirements.html. For more information on system requirements to run rippled, see https://xrpl.org/system-requirements.html.