[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: two problems when migrating from 2.1.30 to 2.2.15

vadim wrote:

Hallo everybody,

I am trying to move from 2.1.30 to 2.2.15. I've met two problems, which
I can not identify as mine at the moment, and I want to know what do you
think about it ...


2) I had string "set_flags DB_LOG_AUTOREMOVE" in my DB_CONFIG file. This
was making berkeley db to remove all unused log files after next
checkpoint. With 2.2.15 this parameter in DB_CONFIG does not make any
effect, log files remain on file system. Do you know if something has
changed?

Yes, in order to fix a locking problem in back-bdb the cache code was changed to use a long-lived transaction per slapd thread to handle read-only operations. Unfortunately BDB 4.2.52 has a bug where these long-lived transactions prevent the DB_LOG_AUTOREMOVE option from working. They also prevent db_archive from doing anything useful.

I posted a patch to BDB 4.2.52 that will allow it to work properly when a special option flag is used in the back-bdb code. 4.3 already works correctly by default, so no special option is needed there, but I don't believe it has been released yet.

There was a long discussion of this problem on the -devel list, you can get some of it here:
http://www.openldap.org/lists/openldap-devel/200407/msg00051.html

The patches are in this message:
http://www.openldap.org/lists/openldap-devel/200407/msg00068.html

Keep in mind that if you use these patches, you will need to undo the patch to back-bdb when you migrate to BDB 4.3.
--
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
http://www.symas.com http://highlandsun.com/hyc
Symas: Premier OpenSource Development and Support