Skip to main content Ripple validator returns normal since two day ago

There's been some problems with the validator ever since it crashed about a week ago. It doesn't crash any more since I added much more disk space. But it easily falls behind and needs to play catch up several hours after each restart. I learned this from state_accounting field in the output of "rippled server_info". I created a metric and a chart from it. This is what the chart looks for the last week.
The "Full" mode state means it is fully synced and participating in consensus process. You can see it is now asymptotically approaching 100 now. The value means the percentage of uptime the validator stays in each mode.

I figured out why the disk was out of space. It was because the validator fell behind. When that happens, online delete is disabled. See this code:

I saw some "Not deleting" messages in the log which led me to the above code.

I still can't determine the exact reason why it fell behind. I suspect it was caused by some "insane" testnet peer. So I blocked some peers with iptables. But now it's almost 100% full and it still has an insane testnet peer.

However I do know why it didn't recover after disk is enlarged. I believe it's because I changed the db to NuDB from RocksDB and still have online_delete set in the config. I changed it because I learned NuDB works better on SSD. But it doesn't support update or delete. It is meant to be used in full history validator. It appears that when it tries to do online_delete, it starts to fall behind. Now I have switched back to RocksDB and everything is fine.


Popular posts from this blog

You have to know these about ripple wallet and secret key


It's possible to find out others' secret keys but it's so improbable that it's almost impossible. Make sure you have a good entropy source when generating your address/secret key.Use multi-sign
See the discussion here:

Several possible attacking modes on XRP ledger

There are several degrees of damage, that trusted validators can do (if they decide to give up their hard-earned trust), in increasing difficulty order:
If a set of them, each of which only trust others in the same set, with less than 20% of them trust validators not in that set, decide to collude, they can create fork.If more than 20% of them decide to collude, they can prevent transactions from being validated.If more than 80% of them decide to collude, they can rewrite history as they wish. 
However, as pointed out by mDuo13@, creating a fork is easy, but making people accept it is hard.

Illinois Is Venezuela and the Solution Is Cryptocurrency

What this article really is trying to say is, the "real" money is inflationary in nature and they are being manipulated throughout its not so long history and you have no control over that.

On the contrary, cryptocurrencies (e.g. Bitcoin) are not inflationary (XRP is even deflationary).

This difference makes the latter will increase in value in terms of the "real" money inevitably.

So, buy the fucking every dip of cryptocurrencies and HODL!