[elephant-devel] wedging elephant

[Ben]

i've managed to make elephant / sleepycat unresponsive by not properly
shutting it down or misusing the connections, or breaking the
threading contracts.  (aborting transactions for me is usually pretty
safe.  maybe some lisps interrupt foreign calls and others don't?)
i've personally never gotten segfaults.  what do you mean by "slot
errors on the store controller?"

in general when i'm careful to use sleepycat as the docs dictate, it
works ok.  it's a little hard, especially in an interactive session,
to write macros which guarantee correct usage, since typically
connections stay open for a long while, so "with-open-file" doesn't
make sense.

i have personally never run into a situation where recovery didn't
work.  sleepycat has gotten a "bad reputation" amongst people who i
tend to think are less than careful -- e.g. in the movable type
community, i think.  i think amongst people who care, like DBAs, it's
considered reliable.

i hope this answers your question.

take care, B

On Mon, 15 Nov 2004, Zach Beane wrote:

> Through the course of messing around I've managed to wedge elephant a
> few times. Symptoms include unresponsive lookups (things seem to just
> hang), slot errors on the store controller, and once, incessant
> segfaults. I think I caused these in a few different ways, such as
> interrupting and aborting actions in progress, and not cleanly
> shutting down the connection. I might have done other things too.
>
> So, what are some good ways to prevent wedging? What sorts of behavior
> should I avoid? What's the worst thing that can happen? Might I lose
> all my data? Is recovery reliable?
>
> Zach
>
>
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>