How do other Subversion administrators manage (or prevent) excessive
repository growth?
I recently had to dump, filter, and reload a huge repository (19GB!!).
Of course this was an extreme case, but it made me really wish I had the
ability to "obliterate" revisions.
See the entry for in the issue tracker for issue #516:
http://subversion.tigris.org/issues/show_bug.cgi?id=516
I recognize that this is probably a complicated problem to solve, but it
also appears that most people feel it is a necessary addition to the
Subversion administrator's toolkit.
Here is some example situations (from my perspective):
1. people can develop patterns of use that, over time, will
cause repositories to become huge
2. sometimes people commit sensitive data to the repository
In the first situation, of course, training about the persistence of
data in the repository helps.
On the other hand, even smart, well-trained people can inadvertently
commit garbage.
The second situation is something that we must deal with from time to
time.
The dump-filter-reload approach works, with some hiccups, but it is
expensive in terms of time and space.
I'd like to hear other administrators solutions to monitoring and
containing repository growth.
For instance, since sourceforge now hosts a lot of subversion
repositories, what are their tricks?
Thanks,
Mark Johnson
Corillian Corp.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 9 22:17:02 2006