Running IPFS with multiple servers on one Repo
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
#### Version information:
go-ipfs version: 0.4.19-
Repo version: 7
System version: amd64/linux
Golang version: go1.11.5
root@production-69b4566cc
Docker on Kubernetes running mostly urlstore.
#### Type: doc ?
#### Description:
We (Internet Archive) are running IPFS in a docker instance under Kubernates - which can power up servers as required for load, in case of failure etc, but has a number of constraints.
In order to persist IPFS across times the server is restarted we mount the repo from a persistent storage volume.
We'd like to configure Kubernates to spin up multiple servers if load spikes (as it does whenever someone does a live demo of dweb.archive.org for example). BUT I'm concerned that two servers hitting the same repo would corrupt it and can't find any info (https://github.com/ipfs/go-ipfs#docker-usage being the obvious place).
Is running this kind of installation covered anywhere, or is it too weird to be common - in which case does anyone know whether IPFS for example uses appropriate locks to stop conflicts when two or more servers share a repo ?
Note that we are almost entirely using IPFS with urlstore, if that makes any difference, but I think the question deserves a general answer (probably in the Docker section of the README).
Contributor guide
Assessment
This issue has not been assessed yet.