XRP Ledger version 1.4.0 Upgrade Advisory
Version 1.4.0 of the XRP Ledger core server (
rippled) contains a change that can cause upgrades to take much longer than usual.
When upgrading to version 1.4.0,
rippled automatically reorganizes its SQL databases to remove some unused data. This happens during startup the first time the server runs after upgrading to 1.4.0. The SQL reorganization should complete within 10 to 20 minutes for most servers. For servers that have been running for longer than a few months, the operation may take significantly longer. During this time, your server will not be usable.
Plan accordingly for the time that this upgrade may take.
If you currently use a single
rippled server, consider instead running two or more independent
rippled servers to avoid downtime while one server is being upgraded. (Do not run more than one validator.)
Database Reorganization Details
Previous releases stored data in a "Validations" table in the SQLite data store. This data is not needed, so
rippled 1.4.0 drops (deletes) the Validations table, if it exists. Dropping the Validations table can take many, many hours, depending on how large the Validations table is. This varies based on the server's configuration and how long it has been collecting past history. During this time, the rippled server is unable to operate or serve requests.
If needed, a workaround is possible. However, we do not recommend this procedure if you are not familiar with sqlite3.
The following workaround can reduce
rippled's initial startup time after upgrading to version 1.4.0. It requires making changes to one of the SQL databases maintained by the server. Instead of deleting the unneeded data, this workaround renames the table. The old data continues to take up disk space on the server.
WARNING: We do not recommend this procedure to anyone not familiar with sqlite3.
Install the required tool:
sqlite3. This is operating-system dependent.
On Ubuntu you can use the following commands:
sudo apt-get update sudo apt-get install sqlite3
This is operating-system dependent. On Linux, you can use the following commands:
sudo systemctl stop rippled.service
Read your configuration file and find the
On Linux, the configuration file is usually located at
The directory in the
[database_path]stanza is where your server stores its SQL databases.
Change to a user that has permissions to read and write files in the SQL database directory you found in the previous step.
On Linux, you can use the
ledger.dbfile using the SQLite commandline:
Execute the following command (the trailing semicolon is required):
ALTER TABLE Validations RENAME TO OldValidations;
Execute the following command (the leading period is required):
You should now be able to start
rippledwithout experiencing any delay.
sudo systemctl start rippled.service
For general instructions on upgrading
rippled on supported platforms, see Install
Learn, ask questions, and discuss
To receive email updates whenever there are important releases or changes to the XRP Ledger server software subscribe to the ripple-server Google Group.
Related documentation is available in the XRP Ledger Dev Portal, including detailed example API calls and web tools for API testing.
- The XRP Ledger Dev Blog
- Ripple Technical Services: [email protected]
- XRP Chat Forum