Every time clio finishes processing a ledger, clio should send a can_delete request to rippled, with can_delete set to the ledger which clio just processed. This tells rippled that it's safe to delete that ledger from it's nodestore.
rippled may respond with a notEnabled error, if advisory deletion is not enabled. However, I think clio should just keep sending these messages, because the rippled node could be restarted with an updated config, and the messages are tiny.
This will require a new method in ETLLoadBalancer that sends a websocket request to ALL of the connected rippled nodes, instead of one at random.
Every time clio finishes processing a ledger, clio should send a
can_delete
request to rippled, withcan_delete
set to the ledger which clio just processed. This tells rippled that it's safe to delete that ledger from it's nodestore.rippled may respond with a
notEnabled
error, if advisory deletion is not enabled. However, I think clio should just keep sending these messages, because the rippled node could be restarted with an updated config, and the messages are tiny.This will require a new method in
ETLLoadBalancer
that sends a websocket request to ALL of the connected rippled nodes, instead of one at random.