Hi, we have times where the load of our server is getting quite high, so we want to spread the load to different svn-instances. As we have TBs of data, we do not want to share these data over different storages.
But if you say, that (one) shared storage with different svn-instances (mod_subversion) will never work, than ok, I didn't find an answer. Can you confirm? If yes, then we have to thing about a different architecture, eg. many svn-instances each with its own storage regards Jonathan -----Ursprüngliche Nachricht----- Von: Branko Čibej <br...@apache.org> Gesendet: Freitag, 23. November 2018 12:06 An: users@subversion.apache.org Betreff: Re: SVN on docker/kubernetes/openshift - shared storage? On 23.11.2018 11:27, Tietz, Jonathan wrote: > Hi, > > we are thinking about to run subversion on a docker/openshift environment. > > That means we have multiple subversion instances, reading/writing on > subversion repositories saved on one shared storage (currently nfs > filesystem) > > According to internet, e.g. > https://support.wandisco.com/index.php?/Knowledgebase/Article/View/182 > /0/why-you-should-not-use-network-file-system-with-git-or-svn > You should not use nfs. > > Has someone else running a similar setup with a shared storage? If yes, what > filesystem are you using? What are you trying to achieve with this configuration? Perhaps there's a better way to solve your use-case than using a basically unsupported and possibly broken configuration. -- Brane
