slow cn=config changes; Re: Correct procedure to backup LDAP?

2006-08-14 Thread Eric Irrgang
I'm trying to migrate to a reliable live update mechanism and I have tried using slapcat after putting the directory into read-only mode, but that seems to bring up additional issues. In OL 2.3.24 with hdb, how supported is it to do the following? $ ldapmodify dn: olcDatabase={1}hdb,cn=config c

Re: slow cn=config changes; Re: Correct procedure to backup LDAP?

2006-08-14 Thread Howard Chu
Eric Irrgang wrote: I'm trying to migrate to a reliable live update mechanism and I have tried using slapcat after putting the directory into read-only mode, but that seems to bring up additional issues. In OL 2.3.24 with hdb, how supported is it to do the following? $ ldapmodify dn: olcDataba

Re: slow cn=config changes; Re: Correct procedure to backup LDAP?

2006-08-14 Thread Aaron Richton
Howard's spoken well to the internals of back-config. I'll note: (a) it's supposed to be safe to slapcat the hot 2.3.24 hdb, but I'm hoping you know that and therefore you want to snapshot at quiescent state only (b) if I was trying to take a snapshot of the directory at precisely one time, I

Re: slow cn=config changes; Re: Correct procedure to backup LDAP?

2006-08-14 Thread Howard Chu
Howard Chu wrote: Eric Irrgang wrote: I'm trying to migrate to a reliable live update mechanism and I have tried using slapcat after putting the directory into read-only mode, but that seems to bring up additional issues. In OL 2.3.24 with hdb, how supported is it to do the following? $ ldapm

Re: slow cn=config changes; Re: Correct procedure to backup LDAP?

2006-08-15 Thread Howard Chu
Eric Irrgang wrote: On Mon, 14 Aug 2006, Howard Chu wrote: I should note that for this specific example, you can also set readonly mode using cn=monitor, which has no particular impact on the thread pool, so it should take effect immediately. Okay, that I don't understand. Are you still talk

Re: slow cn=config changes; Re: Correct procedure to backup LDAP?

2006-08-15 Thread Eric Irrgang
On Mon, 14 Aug 2006, Howard Chu wrote: Howard Chu wrote: This sounds pretty normal. When you issue a modify on cn=config, it suspends the thread pool. That means that no new operations can start, and cn=config waits for any currently running operations to finish, then it does the modification

Re: slow cn=config changes; Re: Correct procedure to backup LDAP?

2006-08-16 Thread Pierangelo Masarati
Howard Chu wrote: I should note that for this specific example, you can also set readonly mode using cn=monitor, which has no particular impact on the thread pool, so it should take effect immediately. back-config should be used for __persistent__ changes to configuration; back-monitor for __tr