Sleepycat and CollabNet Open Source Collaboration
Posted Feb 9, 2006 5:08 UTC (Thu) by Peter
In reply to: Sleepycat and CollabNet Open Source Collaboration
Parent article: Sleepycat and CollabNet Open Source Collaboration
Yeah, I can only think it means "automatic" in the sense of
"whenever anything goes wrong, the system administrator will automatically
go through a full recovery process
While I appreciate the cynicism, they really do mean automatically.
This code was tested by doing normal subversion stuff but also having a
thread running whose only purpose was to start a transaction then get kill
-9'd. Once per second, or was it 10 times per second? Anyway, the ability
for an application to avoid wedging the DB even when dying unexpectedly is
new to DB 4.4, so your previous experiences aren't completely valid.
The annoying part of this announcement is that we are in the
process of switching from CVS to SVN. I'll have to find out what this
means w.r.t. the impact on reliability.
DB isn't the default backend. Most people recommend the FSFS backend
instead, which is why it's the default. It's a little slower for some
operations, and creates a huge directory (one file per revision, just like
arch, so if you have 25000 revisions you get a dir with 25000 files, which
doesn't perform well with certain filesystems), but it has the very nice
property of not changing your old data - think of it as an append-only
system. And it works over NFS, not that we'd necessarily recommend it.
to post comments)