On Nov 7, 2008, at 02:03, <sandeep.saxena_at_rbs.com>
<sandeep.saxena_at_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_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-08 07:21:08 CET