is it possible to have datadir over network instead of disk?

[pocesar]

I'm trying to figure out a way to reuse existing blockchain database to multiple spot instances, so I don't have to download the blockchain per each spot instance everytime they go up on auto scaling on AWS. The thing is, datadir needs a disk path, how could I create a on-demand instance to keep the blockchain so each spot instance can take advantage with the lastest blockchain? would many daemons writing to the same blockchain database be a problem?

like so:

Code:

 
                                                    /--> [spot instance with daemon]
[frontend] ---> [blockchain / pool load balancer]  <-->  [spot instance with daemon]
                                                    \--> [spot instance with daemon]

[justusranvier]

In principle you should be able to use NFS to share the directory containing the blockchain.

Or you could use Bits of Proof instead of bitcoind, which was explicitly designed for that kind of thing.

[kostagr33k]

From the research  I have done, I believe you can have one master (two for safety) that are online 100% of the time, and each secondary node "slave" off of the masters. That way, when the slave needs any information, it will query one of the masters.

If that is something that will work in your infrastructure, I would google that.


If you can't figure it out, feel free to PM me.


kosta

[jdbtracker]

Build a Hadoop cluster and distribute the hard drive over a network and connect it. It could work.

[pocesar]

the only thing that I haven't actually tried is that if the underlaying database used in bitcoind / bitcoin-qt has some sort of locking. if 2 or more daemons are connected to the network, they will (expected) receive the same info from the network, and try to work the same data to the database, right?

[kostagr33k]

Try adding this to your Slave bitcoind Node config:

Code:

rpcconnect=MasterIP 
connect = 0.0.0.0

rpcconnect Means all commands from the Slave, will "proxy" to the MAster Node

connect=0.0.0.0 Tells the Slave node not to connect to the Network and NOT download the chain.


That should let you setup Slave bitcoind Nodes that you can have throughout your network.