What happens when the storage at 'LOTUS_PATH' runs out? #9341
-
Still trying to get my head wrapped around managing the data store for a lotus node. I am mostly using it as a means to interact with the command line wallet without relying on a remote node. I would like to avoid committing too much space to it for this limited use case. I know there is a way to stop the node compact and re-sync every so often and suppose that this could be automated. But I was wondering what would happen if you simply let it run out of space. Does it crash? Does it clean up after itself? semi-related, would be nice to have a rolling snapshot that maintains the lightweight state of current block minus 2000. Rather than building on top of lightweight store , it would take a first in first out approach and deletes the oldest block with every new block added. I will admit, not a whole lot of thought has been put into this on my end. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
For the Lotus node, you never want to run out of disk space. One good solution is to use the split store feature for the chain and then separate the cold store [chain] and symlink it to a larger HDD. Keep the rest of the chain (splitstore) on fast disk like NVMe.
|
Beta Was this translation helpful? Give feedback.
For the Lotus node, you never want to run out of disk space. One good solution is to use the split store feature for the chain and then separate the cold store [chain] and symlink it to a larger HDD. Keep the rest of the chain (splitstore) on fast disk like NVMe.
du -sch .lotus/datastore/* | sort -rh