AW: AW: SVN on docker/kubernetes/openshift - shared storage?
From: Tietz, Jonathan <jonathan.tietz_at_siemens.com>
Date: Thu, 29 Nov 2018 13:03:56 +0000
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
these method are for read only:
All others are for write operations
On 27.11.2018 11:25, Tietz, Jonathan wrote:
The first step is to find out what exactly is causing the load; whether it's commits or updates or something else.
> As we have TBs of data, we do not want to share these data over different storages.
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.
> If yes, then we have to thing about a different architecture, eg. many
Sure, you can split repositories amongst different servers. Or you can use a commercial solution that provides master/master replication.
> -----Ursprüngliche Nachricht-----
This is an archived mail posted to the Subversion Users mailing list.