I was skeptical about sharing a datadir for multiple bitcoind running on single host (in containers). [Sharing because it saves disk bandwidth and space]

Because older blocks are immutable, they should not be a problem. I think current block or temp block that is being accessed by multiple nodes for writes can cause problems.

Appreciate any help!

  • Why would you want to have multiple bitcoind on a single host? – Anonymous Dec 26 '18 at 20:25
  • it's intended to be used by multiple people. They want to run their own nodes and in order to make resource utilization better, we want to colocate and want to share blockchain data. – Sanket Patel Dec 27 '18 at 8:00
  • You sort of can't do this. A ZFS backing will let you de-duplicate some nodes in specific setups, but you can't have multiple nodes using the same blocks or data directory. Functionally the software is not designed for this sort of usage, so you won't find a lot of help in using it this way. What does the customer get from using their own node, versus using a single shared one? – Anonymous Dec 27 '18 at 8:01
  • customer can launch node with their own configuration. Closest we can get to reusability is to copy blockdata while bootstrapping new node but it has to be independent once they are running. Right? en.bitcoin.it/wiki/Data_directory#Transferability – Sanket Patel Dec 27 '18 at 10:46
  • What configuration options do you consider them to be changing? Your answer is to use ZFS to deduplicate the blocks but like, this doesn't make sense at all from the consumer or product side of things. – Anonymous Dec 27 '18 at 18:49

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.