Hi Brane,
thanks for your response.
To understand you right, if we are using many svn-instances and one shared storage AND we are using a loadbalancer, we have to ensure that write operations will only be done on ONE svn-instance.
That means we have to choose between http method. I found one sample for HAProxy
https://stackoverflow.com/questions/34916975/haproxy-rewrite-http-requests-based-on-http-method
these method are for read only:
GET PROPFIND OPTIONS REPORT
All others are for write operations
regards
Jonathan
-----Ursprüngliche Nachricht-----
Von: Branko Čibej <***@apache.org>
Gesendet: Dienstag, 27. November 2018 20:44
An: ***@subversion.apache.org
Betreff: Re: AW: SVN on docker/kubernetes/openshift - shared storage?
Post by Tietz, JonathanHi,
we have times where the load of our server is getting quite high, so we want to spread the load to different svn-instances.
The first step is to find out what exactly is causing the load; whether it's commits or updates or something else.
Post by Tietz, JonathanAs 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?
Subversion itself supports master/slave replication, where all commits go to a single server but read operations can be served by many. Maybe that's sufficient for your case, but it's hard to say without any performance data. Sometimes just tuning the server configuration may be enough.
Post by Tietz, JonathanIf yes, then we have to thing about a different architecture, eg. many
svn-instances each with its own storage
Sure, you can split repositories amongst different servers. Or you can use a commercial solution that provides master/master replication.
-- Brane
Post by Tietz, Jonathan-----Ursprüngliche Nachricht-----
Gesendet: Freitag, 23. November 2018 12:06
Betreff: Re: SVN on docker/kubernetes/openshift - shared storage?
Post by Tietz, JonathanHi,
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/18
2 /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 poss