Strangeness with post-commit script

[Gary Thomas <ga...@mlbassoc.com>]

I've modified my post-commit script to periodically do
a complete repository dump.  The repository is rather large;
700 or so revisions and the compressed dump is around 300MB.
The odd thing is that the post-commit script fires up the
dump (in the background so the client commit finishes right
away).  It then runs for a while (maybe 15 minutes) and then
freezes up - just sits there.  I have no troubles running
the dump manually.

I'm running this from Apache on Linux (Red Hat 9)

Any ideas?

Thanks

--
Gary Thomas
MLB Associates


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

Re: Strangeness with post-commit script

[Gary Thomas <ga...@mlbassoc.com>]

Ben Collins-Sussman said:
>
> On Dec 15, 2004, at 6:57 AM, Gary Thomas wrote:
>
>> I've modified my post-commit script to periodically do
>> a complete repository dump.  The repository is rather large;
>> 700 or so revisions and the compressed dump is around 300MB.
>> The odd thing is that the post-commit script fires up the
>> dump (in the background so the client commit finishes right
>> away).  It then runs for a while (maybe 15 minutes) and then
>> freezes up - just sits there.  I have no troubles running
>> the dump manually.
>>
>> I'm running this from Apache on Linux (Red Hat 9)
>>
>> Any ideas?
>>
>
> I have no idea about the freeze... but it seems pretty unwise to do
> such a huge, time-consuming task in a post-commit script.  What happens
> if 3 commits all happen in the space of a minute?

I only do the dump for every 10 commits, so this is not really a problem.
On each other commit, I do a dump of just the revision/change.

>
> If you're trying to design a backup strategy, you should probably do
> something simpler and quicker in post-commit... like do an 'svnadmin
> hotcopy' (which is quick, because it's basically like running 'cp -R'
> on the repository)... or perhaps only dump just the newly committed
> revision, so you end up with a bunch of incremental dumpfiles.  Save
> the 'full dump' stuff for a nightly cron job.

I really only want the full dumps to take place after a commit.  I have
regular file system backups as well.

Also, after all the troubles I had before with my repository becoming
useless after just one commit, I want a 100% foolproof way to rebuild
it to known points at all times.

Thus the desire to take periodic dumps.

---
Gary Thomas
MLB Associates


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

Re: Strangeness with post-commit script

[Ben Collins-Sussman <su...@collab.net>]

On Dec 15, 2004, at 6:57 AM, Gary Thomas wrote:

> I've modified my post-commit script to periodically do
> a complete repository dump.  The repository is rather large;
> 700 or so revisions and the compressed dump is around 300MB.
> The odd thing is that the post-commit script fires up the
> dump (in the background so the client commit finishes right
> away).  It then runs for a while (maybe 15 minutes) and then
> freezes up - just sits there.  I have no troubles running
> the dump manually.
>
> I'm running this from Apache on Linux (Red Hat 9)
>
> Any ideas?
>

I have no idea about the freeze... but it seems pretty unwise to do 
such a huge, time-consuming task in a post-commit script.  What happens 
if 3 commits all happen in the space of a minute?

If you're trying to design a backup strategy, you should probably do 
something simpler and quicker in post-commit... like do an 'svnadmin 
hotcopy' (which is quick, because it's basically like running 'cp -R' 
on the repository)... or perhaps only dump just the newly committed 
revision, so you end up with a bunch of incremental dumpfiles.  Save 
the 'full dump' stuff for a nightly cron job.


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