| |||||||||||||
Sleepycat and CollabNet Open Source CollaborationSleepycat and CollabNet Open Source CollaborationPosted Feb 8, 2006 2:48 UTC (Wed) by jwb (guest, #15467)Parent article: Sleepycat and CollabNet Open Source Collaboration
Wait, how the HECK do you get automatic recovery from BDB? I have a single-reader multiple-writer database system, and any time any process is killed (be it reader or writer) the whole system wedges until an administrator can issue db_recover. I'd LOVE to know how to get this automatic recovery.
(Log in to post comments)
Sleepycat and CollabNet Open Source Collaboration Posted Feb 8, 2006 6:27 UTC (Wed) by ctg (subscriber, #3459) [Link] Yeah, I can only think it means "automatic" in the sense of "wheneveranything goes wrong, the system administrator will automatically go through a full recovery process because he/she knows there isn't any point in trying to troubleshoot the system". db4 is the most unreliable DB system I've ever come across - not that it has failures, but that the smallest problem seems to cause the most major impact. Impossible to work what is going wrong - everything hangs - sometimes shutting the system down and doing a db_recover doesn't always work - and a full dump and restore is required. I've switched to sqlite3 - which is a bit slower but seems to work - working/slow is better than fast/broken. 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.
Sleepycat and CollabNet Open Source Collaboration Posted Feb 8, 2006 6:42 UTC (Wed) by Dom2 (guest, #458) [Link] To be honest, I'd still choose the FSFS over the DB4 backend. The main advantage is that becauseit's bundled with subversion, something else upgrading your DB4 libraries won't suddenly stop your version control system from working. Unfortunately, this did happen to me. I switched to FSFS when subversion 1.1 came out and I haven't looked back...
But I still love subversion. :-)
-Dom
Sleepycat and CollabNet Open Source Collaboration Posted Feb 9, 2006 5:08 UTC (Thu) by Peter (guest, #1127) [Link] 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.
Sleepycat and CollabNet Open Source Collaboration Posted Feb 9, 2006 8:51 UTC (Thu) by georgm (guest, #19574) [Link] Ok, but what about file stability over releases?I don't want to always get into trouble when switching to a newer db-Version. I had these problems for 2 or 3 times, then I switched to fsfs to avoid this problem.
Sleepycat and CollabNet Open Source Collaboration Posted Feb 9, 2006 4:58 UTC (Thu) by Peter (guest, #1127) [Link] Wait, how the HECK do you get automatic recovery from BDB? That's what this news release is about! Using new features of BDB 4.4,
it's now possible for the app to do this. Previously it was not. The
Subversion BDB backend was recently hacked on for awhile (the
By the way, I believe there's an error in the press release. They say
the new stuff will be in Subversion 1.3.1, but last I heard, that's not the
plan.
|
|||||||||||||