#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Oct 2009
    Posts
    1
    Rep Power
    0

    OpenLDAP 2.3 Resilience Issue


    Hi All,

    We are facing some problem related with Open LDAP replication. The issue is detailed below:

    We are using Open Ldap version 2.3 and slurpd approach for replication.
    We have two LDAP servers in Master-Slave mode. Master Server 1 has read and write access and Slave Server 2 has only read access.A load balancer is configured to handle the load.

    We are getting 'EntryNotFoundException ' exception as soon as we try to read the newly written entry from Server 2. This is the case because the newly written entry is not yet replicated in the Slave Server 2. We wanted to know, is there any approach using which we can forward our search request to Master Server, if the search couldn't find an entry in the Slave Server?

    We have gone through with Referral and Chaining approach, but couldn't find any configuration details using which we can handle this scenario.

    Any pointer to solve the above issue will be of great help to us.
  2. #2
  3. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Nov 2009
    Posts
    1
    Rep Power
    0

    Whats the solution to this issue?


    Hello Rajiv,

    Did you get some solution to this issue? If Yes, Please respond ASAP.
    Would be great, if you can send the configurations at kamal.dodeja at gmail dot com.

    TIA

    Best Regards,
    KD

    Originally Posted by gotorajiv
    Hi All,

    We are facing some problem related with Open LDAP replication. The issue is detailed below:

    We are using Open Ldap version 2.3 and slurpd approach for replication.
    We have two LDAP servers in Master-Slave mode. Master Server 1 has read and write access and Slave Server 2 has only read access.A load balancer is configured to handle the load.

    We are getting 'EntryNotFoundException ' exception as soon as we try to read the newly written entry from Server 2. This is the case because the newly written entry is not yet replicated in the Slave Server 2. We wanted to know, is there any approach using which we can forward our search request to Master Server, if the search couldn't find an entry in the Slave Server?

    We have gone through with Referral and Chaining approach, but couldn't find any configuration details using which we can handle this scenario.

    Any pointer to solve the above issue will be of great help to us.

IMN logo majestic logo threadwatch logo seochat tools logo