hey guys!
* TLDR; this is an attempt to make it faster to download the blockchain on servers running core or forks. so if you know a better solution, please point me to it.
I had an idea, but wanted to see if there's something already done for this that I'm unaware of. Imagine you want to deploy servers that are running core or forks of it. They all have similar data dir:
-rw------- 1 root root 342320183 Jan 25 22:03 blk0001.dat
drwx------ 3 root root 102 Jan 25 05:12 database
-rw------- 1 root root 0 Jan 25 05:12 db.log
-rw------- 1 root root 28267003 Jan 25 22:03 debug.log
-rw-r--r-- 1 root root 77 Jan 25 05:13 <yourfavoritecoinhere>.conf
-rw------- 1 root root 72026 Jan 25 22:03 peers.dat
-rw------- 1 root root 144 Jan 25 17:06 smsg.ini
drwx------ 17 root root 578 Jan 25 19:30 smsgDB
drwx------ 134 root root 4556 Jan 25 22:03 txleveldb
-rw------- 1 root root 69632 Jan 25 21:24 wallet.dat
I was wondering if, there may be a way to have some of the blockchain related files actually coming from a persistent volume or stateful set, so you can basically mount (on a single kubernetes cluster) the same blockchain across multiple instances. It would be "centralized" in some sense, but only on your cluster - but the main point is actually to be able to spawn these services rapidly *without* having to download the entire blockchain.
Please let me know if this idea is worth pursuing of if there is a tried and true way people have been doing this! thanks
