rippled
rippled copied to clipboard
XRPLF
Rippled having lots of issues with syncing to the network (ripple:1.8.1 )
Hi,
We are running rippled node version 1.8.1.
Recently node is having tons of issues with being synced to the network. It is synced for some time, but then after while it is losing sync and stop responding which is affecting pushing txs to the network or getting confirmations.
Now we are receiving lots of such errors:
message:
2021-Dec-24 10:46:38.236278626 UTC LedgerHistory:ERR MISMATCH cannot be analyzed: builtLedger: 9BD1B1C8FF037F432C1FC3911258C172DE76328425E31F728C34119DB8A1B0A8 -> 0x7f97c8128730 validLedger: 1FEF2A74BC66C2954706070F1A05A51A40570DD80EE39273F586745A88D5DE77 -> 0
and
2021-Dec-24 10:46:33.191481524 UTC LedgerHistory:ERR MISMATCH: seq=68543935 validated:5B5196814A17B087294C3FE25F7402E2786D104A244FB4669C1795BD49981730 then:8F57BE99802D3AE07552C04C4FD0E23CF7FAF2B31153B9F48957614EE1A0978B
Is it possible to have some kind of solution for this. Tried to increase IOPS and hardware for host where node is running, but seems like it did not help.
Would appreciate some input on this. Thank you!
Can it be that online_deletion is influencing the performance of how the node is running and making it not operational due to additional load (online_deletion) ?
It would be nice if someone can help on it as I am not sure if it is config issue or general network problem.
We had the same problem and solution was to increase resources. The network got bigger and the old setups are not valid anymore. Some efficient mechanisms are needed.. DEVS, please do something!
