[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: ldapdelete recursive (-r) with syncrepl
- To: Frank Crow <fjcrow2008@gmail.com>
- Subject: Re: ldapdelete recursive (-r) with syncrepl
- From: Quanah Gibson-Mount <quanah@zimbra.com>
- Date: Wed, 13 Apr 2016 08:51:46 -0700
- Cc: Michael Ströder <michael@stroeder.com>, "openldap-techn." <openldap-technical@openldap.org>
- Content-disposition: inline
- Dkim-filter: OpenDKIM Filter v2.10.3 edge02.zimbra.com 7B818A6250
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zimbra.com; s=C2AA288C-EE47-11E2-9BB0-E820BDD9BDBF; t=1460562714; bh=uwRmG0DefR4hwSMh/DqNZDb334silbLm4pM2pbTwJ7Q=; h=Date:From:To:Message-ID:MIME-Version; b=e2XflhajJrSQpCaCm8N/87maaZNJWdbn5ezqcKYz6fnFxLL1PrZ52pE8oFzUAUV7q k3pU/F5mupqj412ovHsnce6+CRC8Ph2sfKKGk7GKCyK2Lg/txhkPofPXXlWiCbj12+ Q89+K+5+mTTqAifIvsooZ/+Rh7FbO3/cV40HC+nE=
- In-reply-to: <CAB+L7Ken0rE1H0=1yp2FamLoFf6K6+ouN97ji1rbBrK9rGjoow@mail.gmail.com>
- References: <CAB+L7Kenae8mVbFqZDWY+4XU-zYuVyS10tkYpyA9OzzmnwT4qA@mail.gmail.com> <570D6CE5.4090202@stroeder.com> <CAB+L7KdaPyze8rmnQvDegKxAJBc2ZaOhhaPReNk4c-wXd2sPKA@mail.gmail.com> <570DE3E4.1070906@stroeder.com> <CAB+L7KciDqibodaacPNi28o6V3Lv-Z2zx=qUgSppo1Shoxvx-A@mail.gmail.com> <802FD1B93AD8FE416B254437@192.168.1.19> <CAB+L7Ken0rE1H0=1yp2FamLoFf6K6+ouN97ji1rbBrK9rGjoow@mail.gmail.com>
--On Wednesday, April 13, 2016 12:29 PM -0400 Frank Crow
<fjcrow2008@gmail.com> wrote:
Well, OK. Our formal test procedures (created and executed by a
separate team) will intentionally do all manner of destructive changes to
the DIT after taking a snapshot. After which they want to clean and
reload the entire DIT in order to: 1) be able to run the tests multiple
times with the same data, and 2) restore the DIT for normal (non-OpenLDAP
related) testing that does need the DIT intact.
Then just slapcat the data first, do your destructive tests, and then
restore from slapadd. Doing repetitive ldap deletes/adds will just causes
massive database growth.
During production use, we would not be doing that. For that, I think
the individual node repair (slapadd/slapcat) would be exactly what we
need.
I took your suggestion and forwarded the list of changes since 2.4.40
(with the syncrepl fixes highlighted) to the important people up the
"flag pole" this morning. I am "fighting the good fight" with them but
they are hesitant to move without strenuous "encouragement!" ;-)
I guess it just depends on whether or not they consider data loss
acceptable. If they do find it acceptable, by all means, stay on 2.4.40. ;)
Also not sure which database backend you're using, but I'd strongly advise
back-mdb once you get to 2.4.44.
--Quanah
--
Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
A division of Synacor, Inc