On Tue, 2018-02-20 at 23:36 +0000, Fong, Trevor wrote: > Hi William, > > Thanks a lot for your reply. > > That's correct - replication schedule is not enabled. > No - there are definitely changes to replicate - I know, I made the > change myself ( > I changed the "description" attribute on an account, but it takes up > to 15 mins for the change to appear in the 1.3 master. > That master replicates to another master and a bunch of other hubs. > Those hubs replicate amongst themselves and a bunch of consumers. So to be correct in my understanding: 1.2 <-> 1.3 --> [ group of hubs/consumers ] Yes? > > The update can take up to 15 mins to make it from the 1.2 master, > into the 1.3 master; but once it hits the 1.3 master, it is > replicated around the 1.3 cluster within 1 sec. > > Only memberOf is disallowed for fractional replication. > > Can anyone give me any guidance as to the settings of the "backoff" > and other parameters? Any doc links that may be useful? Mark? You wrote thisn, I can't remember what it's called .... > > Thanks a lot, > Trev > > > On 2018-02-18, 3:32 PM, "William Brown" <william@xxxxxxxxxxxxxxxx> > wrote: > > On Sat, 2018-02-17 at 01:49 +0000, Fong, Trevor wrote: > > Hi Everyone, > > > > I’ve set up a new 389 DS cluster (389-Directory/1.3.6.1 > > B2018.016.1710) and have set up a replication agreement from > our old > > cluster (389-Directory/1.2.11.15 B2014.300.2010) to a master > node in > > the new cluster. Problem is that updates in the old cluster > take up > > to 15 mins to make it into the new cluster. We need it to be > near > > instantaneous, like it normally is. Any ideas what I can > check? > > I am assuming you don't have a replication schedule enabled? > > In LDAP replication is always "eventual". So a delay isn't > harmful. > > But there are many things that can influence this. Ludwig is the > expert, and I expect he'll comment here. > > Only one master may be "replicating" to a server at a time. So if > your > 1.3 server is replicating with other servers, then your 1.2 > server may > have to "wait it's turn". > > There is a replication 'backoff' timer, that sets how long it > tries and > scales these attempts too. I'm not sure if 1.2 has this or not > though. > > Another reason could be there are no changes to be replicated, > replication only runs when there is something to do. So your 1.2 > server > may have no changes, or it could be eliminating the changes with > fractional replication. > > Finally, it's very noisy but you could consider enabling > replication > logging to check what's happening. > > I hope that helps, > > > > > > > Thanks a lot, > > Trev > > > > _________________________________________________ > > Trevor Fong > > Senior Programmer Analyst > > Information Technology | Engage. Envision. Enable. > > The University of British Columbia > > trevor.fong@xxxxxx | 1-604-827-5247 | it.ubc.ca > > > > _______________________________________________ > > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to 389-users-leave@lists.fedorapro > ject.o > > rg > -- > Thanks, > > William Brown > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@lists.fedoraproje > ct.org > > > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@lists.fedoraproject.o > rg -- Thanks, William Brown _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
