Re: [389-users] Read data immediately after write

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



No i am not talking about proxy server but a master-slave set-up of OpenLDAP 2.3 and need to achieve chaining between them.
 
Cheers,
Ankur


--- On Mon, 10/19/09, Rich Megginson <rmeggins@xxxxxxxxxx> wrote:

From: Rich Megginson <rmeggins@xxxxxxxxxx>
Subject: Re: [389-users] Read data immediately after write
To: "General discussion list for the 389 Directory server project." <fedora-directory-users@xxxxxxxxxx>
Date: Monday, October 19, 2009, 1:04 PM

Ankur Agarwal wrote:
> I want to achieve chaining between a master and slave having exactly same OUs and are based on OpenLDAP 2.3.
>
> What would be the configuration to achieve that?
>   
So 389 is the proxy server and openldap is hosting the real data?  It
should just work.  Have you tried this configuration?  If so, what
problems did you encounter?
> Regards,
> Ankur
>
> Sent from my iPhone
>
> On Oct 14, 2009, at 1:55 AM, Rich Megginson <rmeggins@xxxxxxxxxx> wrote:
>
> Ankur Agarwal wrote:
> Thanks Rich...Would it be possible for you to share some configuration details to achieve this for OpenLDAP version 2.3?
>
> To achieve what exactly for OpenLDAP 2.3?  Chain from 389 to OpenLDAP?
>
> Cheers,
> A
>
> --- On *Mon, 10/12/09, Rich Megginson /<rmeggins@xxxxxxxxxx>/* wrote:
>
>
>    From: Rich Megginson <rmeggins@xxxxxxxxxx>
>    Subject: Re: [389-users] Read data immediately after write
>    To: "General discussion list for the 389 Directory server
>    project." <fedora-directory-users@xxxxxxxxxx>
>    Date: Monday, October 12, 2009, 10:47 AM
>
>    Ankur Agarwal wrote:
>    > Can i use chaining between master-slave without having different
>    "ou"?
>    > I mean if i have exactly same directory structure and same set
>    of OUs
>    > can i still have chaining between master and slave?
>    >
>    Yes.
>    >
>    > Cheers,
>    > Ankur
>    >
>    >
>    > --- On *Thu, 10/8/09, Michael Ströder /<michael@xxxxxxxxxxxx
>    <http://us.mc589.mail.yahoo.com/mc/compose?to=michael@xxxxxxxxxxxx>>/*
>    wrote:
>    >
>    >
>    >     From: Michael Ströder <michael@xxxxxxxxxxxx
>    <http://us.mc589.mail.yahoo.com/mc/compose?to=michael@xxxxxxxxxxxx>>
>    >     Subject: Re: [389-users] Read data immediately after write
>    >     To: "General discussion list for the 389 Directory server
>    >     project." <fedora-directory-users@xxxxxxxxxx
>    <http://us.mc589.mail.yahoo.com/mc/compose?to=fedora-directory-users@xxxxxxxxxx>>
>    >     Date: Thursday, October 8, 2009, 1:38 AM
>    >
>    >     Ankur Agarwal wrote:
>    >     >
>    >     > I have a master-slave set-up with write operations always
>    being
>    >     done to
>    >     > the master node. Now there is an issue where i need to
>    read some
>    >     data
>    >     > immediately after write, and my read request goes to the
>    slave.
>    >     It fails
>    >     > in cases when replication hasnt happened from master to
>    slave before
>    >     > this read operation.
>    >
>    >     You simply should not do that. Read from the master if you
>    have to
>    >     rely on the
>    >     consistency of what you recently wrote to the master.
>    >
>    >     > Is there a LDAP level configuration to handle this situation?
>    >     > Can chaining help in this case?
>    >
>    >     No. (Except chaining the read requests of the writing client to
>    >     the master
>    >     which you don't want I guess).
>    >
>    >     Ciao, Michael.
>    >
>    >     --
>    >     389 users mailing list
>    >     389-users@xxxxxxxxxx
>    <http://us.mc589.mail.yahoo.com/mc/compose?to=389-users@xxxxxxxxxx>
>    >        <http://us.mc589.mail.yahoo.com/mc/compose?to=389-users@xxxxxxxxxx>
>    >     https://www.redhat.com/mailman/listinfo/fedora-directory-users
>    >
>    >
>    >
>    ------------------------------------------------------------------------
>    >
>    > --
>    > 389 users mailing list
>    > 389-users@xxxxxxxxxx
>    <http://us.mc589.mail.yahoo.com/mc/compose?to=389-users@xxxxxxxxxx>
>    > https://www.redhat.com/mailman/listinfo/fedora-directory-users
>    >   
>
>
>    -----Inline Attachment Follows-----
>
>    --
>    389 users mailing list
>    389-users@xxxxxxxxxx
>    <http://us.mc589.mail.yahoo.com/mc/compose?to=389-users@xxxxxxxxxx>
>    https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
>
>
> ------------------------------------------------------------------------
>
> --
> 389 users mailing list
> 389-users@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

>
>
> --
> 389 users mailing list
> 389-users@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
>
>
>       
>
> --
> 389 users mailing list
> 389-users@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>   



-----Inline Attachment Follows-----


--
389 users mailing list
389-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux