Subversion Master Slave sync

[sa...@rbs.com]

When we set master slave for subversion, should we have post commit hook on master server to update all slaves
Or should we have sync command on slaves to pull after a fixed time period.

First approach has the benefit that sync command would only be on server and not on all slaves separately.
But is disadvantageous in the sense that all syncing load would be on the server.

What is the recommended practice?

Regards,
Sandeep.

***********************************************************************************
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
Authorised and regulated by the Financial Services Authority 
 
This e-mail message is confidential and for use by the 
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender 
by replying to it and then delete the message from your 
computer. Internet e-mails are not necessarily secure. The 
Royal Bank of Scotland plc does not accept responsibility for 
changes made to this message after it was sent. 

Whilst all reasonable care has been taken to avoid the 
transmission of viruses, it is the responsibility of the recipient to 
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its 
systems or data. No responsibility is accepted by The 
Royal Bank of Scotland plc in this regard and the recipient should carry 
out such virus and other checks as it considers appropriate. 
Visit our websites at: 
www.rbs.com
www.rbs.com/gbm
www.rbsgc.com
***********************************************************************************

Re: Subversion Master Slave sync

[Ryan Schmidt <su...@ryandesign.com>]

On Nov 7, 2008, at 02:03, <sa...@rbs.com>  
<sa...@rbs.com> wrote:

> When we set master slave for subversion, should we have post commit  
> hook on master server to update all slaves
> Or should we have sync command on slaves to pull after a fixed time  
> period.
>
> First approach has the benefit that sync command would only be on  
> server and not on all slaves separately.
> But is disadvantageous in the sense that all syncing load would be  
> on the server.
>
> What is the recommended practice?


The svnsync command should be called in the master repository  
server's post-commit and post-revprop-change hooks. On http:// 
svnbook.red-bean.com/en/1.5/svn.serverconfig.httpd.html it says:

> After this is done, we configure the master server's post-commit  
> hook script to invoke svnsync on each slave server:
>
> #!/bin/sh
> # Post-commit script to replicate newly committed revision to slaves
>
> svnsync sync http://slave1.example.com/svn-proxy-sync > /dev/null 2>&1
> svnsync sync http://slave2.example.com/svn-proxy-sync > /dev/null 2>&1
> svnsync sync http://slave3.example.com/svn-proxy-sync > /dev/null 2>&1
>



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org