- The XRP Ledger has released rippled 2.2.3 to fix a Full History node failure caused by an SQLite page size issue.
- Full History servers are recommended to update, but validators can stay on 2.2.2 since the new version has no additional amendments.
The XRP Ledger (XRPL) has implemented an essential upgrade to resolve an issue affecting Full History (FH) nodes on the network. The issue that resulted in the failure of FH nodes was due to a limitation in SQLite page sizing. This fix is implemented in the latest version of Rippled, known as Rippled 2.2.3, which is now ready for download.
In the announcement shared by a validator called Vet on X (previously Twitter), the upgrade to rippled 2.2.3 focuses only on the Full History Servers’ problem. Rippled 2.2.3 is aimed at fixing the SQLite database page size issue that was affecting FH nodes. The upgrade is recommended for all Full History servers that use a page size of 4096, ensuring they can operate smoothly without the issues that have been plaguing them.
The fix for #XRP Ledger Full History Servers is merged in an official rippled release of the XRPLF Repository – rippled 2.2.3 and available for installation. pic.twitter.com/Owpd6xPEHx
— Vet
(@Vet_X0) September 15, 2024
Although the issue was not impacting validators, they were still provided with the choice of staying on the previous version, which is 2.2.2, or upgrading to version 2.2.3. They are both compatible as the current release does not include any changes but is rather a release to address the node failure issue.
Full History Nodes Experience Weekend Failures
The problem with Full History nodes came into the limelight over the weekend and has since garnered a lot of interest from the XRP community. Some of the FH nodes that contain the complete record of transactions on the ledger started failing due to SQLite page size limitations. Even though the problem had been reported some years back, it appeared again and resulted in FH node downtime.
Several validators within the XRPL network had flagged the issue weeks before the recent failures, but it did not get the required attention. Even with these failures, consensus and the overall health of the network were not threatened. Validators remained active and working to maintain the XRP Ledger’s functionality.
XRP Cafe founder xrpl Adam pointed out that most public XRPL endpoints did not need a Full History server to get historical transaction data since clio redundancy was in place. However, he noted that the fix should have been done earlier to avoid the FH nodes’ downtime over the weekend.
a lot of talk and panic about FH nodes failing due to a SQLite restriction in page sizing, but here are the facts.
1. This doesn’t affect consensus or the health of the network.
2. With clio redundancy most public XRPL endpoints don’t need a actual FH server to return historical…— xrpl_Adam (@xrpl_adam) September 14, 2024
Community Discusses Impact and Timing of Full History Node Fix
While there are problems with Full History nodes, the XRPL community has been reassured that the overall health of the network and the consensus process is not impacted. Validators, who are essential for the security and consensus of the network, were not affected by the SQLite page size problem.
As previously reported by Crypto News Flash, the XRP Ledger (XRPL) is expected to receive a major update in the third quarter of 2024 with the launch of Multi-Purpose Tokens (MPTs). This development that focuses on the management and efficiency of tokenized assets will introduce several features to the blockchain.
MPTs will enable users to have real-time data on-chain transactions, which will enhance the speed of tracking the transactions. This is anticipated to enhance decision-making processes since the users will be provided with timely information on how to manage their assets.
