Monday, July 2, 2018

[389-users] Expected Write/Read Behavior in a Supplier/Consumer scenario...

Hi,

I am a LDAP newbie and running into a problem with a simple LDAP supplier - consumer scenario. The topology is as follows:

One 389 DS instance is set up as a read-only replica, the second one as read-write supplier. The replication agreement is in place and any LDAP modifications to the consumer are getting the proper referral to the supplier. The modifications (immediate) are also properly replicated back to the consumer.

Question: If I issue a delete operation to a read-only replica, and the delete request ist properly resend to the actual supplier, can I expect (?) that an immediate read to the consumer does not find the deleted object? Or do I have to wait until the supplier initiated replication (immediate) has taken place?

The current behavior his that I still can read back the "deleted" object from the read-only replica until the replication is over. Is that correct behavior? Or can I 'tweak' things that even on a read-only replica a deleted object is immediately not available, even before replication starts.


Thanks in advance,

Artur
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org/message/XJQXBMVNBNGTRAHBRBNVTHDFYGQUV2FG/

No comments:

Post a Comment