standalone and master slave ldap behave differently

To: openldap-technical@openldap.org

Subject: standalone and master slave ldap behave differently

From: Desiree Klecker <desiree.klecker@googlemail.com>

Date: Mon, 20 May 2013 14:42:59 +0200

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=FUin0OTMppeExv3W9Ulvy9fWGjLkuIO0f6cCXVD1gdk=; b=MFLFMKdrKn+ogrR5obGIe+LnSksj4PfD6nIujQxE7VXO2chqZxANd+bMx2Kn37dqK9 qBeul4+5JrabsmSzZzD/ze9j8rVD2Mt0XOsBUxxLufu/eq0jrEmyj6rs+mXOL91+d6SO DwdPNp6Jbd62YiLuSf69hl1Vi1B7vFHZFyG+ly6Segiri0FLO+LdNBHV/HtzO5XwWiLw 2nLO4AsgHiRIu2IaSBuUvJ2f+QwFZMe/uMzIuW532dRSO6tgnC/LQw9D6MeXkIq2Sxvf BaVZzvbGXFQb71zbJKBRMBzrKUfF1AR9OxONhGm/zjloyALp790VX/SVuwQ5qgbQWa4G /4Hg==

Hello,

to update entry persistend in a master slave openldap environment the
following steps are performed using Java :
1. The entry is removed.
2. The entry is created again.

This does not result in faulty behavior using a single/simple OpenLdap
directory.
Using a master slave configuration this results in unpredictable
errors claiming that the item still exists (the remove statement has ran
immediately before) if it is recreated.

I cannot see why the master slave environment should not behave in a
tranparent way. It seems the remove statement was not
executed in complete allthough the call is synchronous.

Which additional information are required to analyse the problem?

Do similar problems exist/ is this a known problem?

Regards,

Desiree