[Date Prev][Date Next]
Re: index corruption problem (ITS#1349)
> Some more info:
> I think we tracked it down to a script of ours that does a
> modrdn on "uid=testuser". At times there are multiple instances
> of this script running.
> Is modrdn threading-safe ?
It should. One problem of that function is it is not transactional.
This means that a failure between a certain set of operations will
leave the dn and the index spaces in a dangling state. I've been
working on that for a while, but as the problem will be outdated
by back-bdb and modrdn should be considered an administrative
operation, to be performed with extra care, I didn't go too deep
into it. Can you detail to what extent the multiple instances of
the entry coexist? I mean, do they show up when looking for
a(n indexed) value they share or when dumping (ldapsearch or slapcat)
Dr. Pierangelo Masarati | voice: +39 02 2399 8309
Dip. Ing. Aerospaziale | fax: +39 02 2399 8334
Politecnico di Milano | mailto:firstname.lastname@example.org
via La Masa 34, 20156 Milano, Italy |