Maxime Besson wrote: > Hi! > > I am running OpenLDAP 2.4.47 with significant write activity (in the > hundreds of modify/add/del ops per second), and a large volume of data > compared to available RAM (about 20G) > > For backups, I am trying to do a live slapcat dump to maintain > availability, and encountered the growth in MDB database size described > in those ITS: > > http://www.openldap.org/its/index.cgi/Software%20Bugs?id=7904 > http://www.openldap.org/its/index.cgi/Software%20Bugs?id=8226 > > > I am however a little puzzled over the rtxnsize option. My understanding > is that this option splits large read transactions (such as backups) > into smaller transactions, allowing freed pages to be reused before the > end of the full operation. This is critical for me because backups take > more than 10 minutes and a significant portion of my MDB file (100G) > gets filled up during that time.
The rtxnsize option only affects LDAP Search operations. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
