[SVN-1595] unscalable transaction removals

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: all
• Fix Version/s: 0.34
• Component/s: libsvn_fs_base
• Labels: scalability
• Assignee: Unassigned
• Reporter: Ben Collins-Sussman
• Created: 07/Nov/03 15:57
• Updated: 27/Oct/18 16:39
• Resolved: 15/Sep/04 08:43

Description

If a commit fails (due to out-of-dateness, or whatever), the client tries to
delete the failed transaction.  According to cmpilato, though, libsvn_fs uses a
single trail to recursively remove the *entire* transaction.  If the transaction
is really big, it's easy for BerkeleyDB to run out of locks.  This is an icky
scalability bug.

(Note that it's also possible for an update to build a really huge transaction
as well, and updates *always* remove their transactions.   So this isn't just
about commits.)