pull down to refresh
Oh yes it could be a problem.
You had too many updates of the channel state, due to instability, restarts, going offline and coming back online in a short period of time.... in other words a shity node.
If is a private node is not so "disastrous" but if is a public routing node, then yes, is a problem in long run.
You could try first a compacting of database to see if you can cleanup some space. If not, then yes, a bigger db channel state could affect the performance and channel can get force closed.
Thanks
So, improving my uptime will make this less of a problem in the future?
Think about how a channel works, as k00b explained very well. Each update is an increase of data stored.
Each update is: state of the channel (offline or online), sats in HTLCs, balances etc almost the whole history is in there, routed or not routed. The more you do, the bigger it is the db.
Now, if you have a good machine for that node, will not be a big problem, but when that db gets too big, then yes, start time will be slower, update will be slower so trouble will come faster than you think and channel will get a nice force closure.
So I strongly suggest to try a compactation procedure before anything else.
idk why Alby is not offering an option to compact the db from their UI. That will be eeasier for the user. Now you will have to dig manually into the belly of your backend node and do it manually, in CLI.
What's the benefit of closing it now when I don't even know if there is a functional issue vs waiting for a force closure?
You start clean and avoid the trouble coming with a FC (longer waiting time, higher fees or even zombie channel etc).
14MB is not so much for a channel, but when you have some hundreds like that, it became a problem. Especially if is a hosted node, not on your own machine with lots of space available.
Ok. It is on my own machine and I only have 10 channels, so it seems like it's probably not a pressing issue yet.
Is a LND node ?
Try compacting the db.
Soon LND will have also a migration to SQlite so will be a real improvement. But anyways, the migration tool will include a compactation process too, so you better be prepared.
Compactation always helps, but is not necessary to do it very often.
Thanks!
That's all the warning says.