On Wed, Nov 22, 2000 at 10:57:46AM -0800, Perrin Harkins wrote:
> We got past these problems and then ran
> into issues with db corruption. If Apache gets shut down with a SIGKILL
> (and this seems to happen fairly often when using mod_perl),
Really? Why? I've not been aware of anyone needing to do that.
> the data can
> be corrupted in such a way that when you next try to open it BerkeleyDB
> will just hang forever. Sleepycat says this is a known issue with using
> BerkeleyDB from Apache and they don't have a solution for it yet. Even
> using their transaction mechanism does not prevent this problem.
Thanks for the info. Are there any other causes apart from SIGKILL?
(I'd expect SIGKILL to cause some problems. If you're needing to use
SIGKILL then there must be another underlying problem with your system.)
> We tried lots of different things and finally have reached what seems to
> be a solution by using database-level locks rather than page-level. We
> still get to open the database in ChildInit and keep it open, with all the
> speed benefits of the shared memory buffer. It is definitely the fastest
> available way to share data between processes, but the problems we had
> have got me looking at other solutions again.
>
> If you do try it out, I'd be eager to hear what your experiences with it
Sure.
Tim.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
