[Date Prev][Date Next]
Re: (ITS#6275) syncrepl taking long(not sync) when consumer not connect for a moment
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#6275) syncrepl taking long(not sync) when consumer not connect for a moment
- From: firstname.lastname@example.org
- Date: Wed, 26 Aug 2009 17:59:26 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
--On Tuesday, August 25, 2009 6:16 PM +0000 email@example.com wrote:
> The issue I'm facing is related, in a general user view, is when I stop
> the secondary Provider2(master 2) for backup purposes using slapcat. The
> Provider1(master 1) continues to provide ldap service where some
> entrances can be created during the time backup is running(no consumer
> from Provider 2).
Why are you stopping the provider to do a slapcat?
> Even a small number of entrances are different when consumer in Provider 2
> connects to Provider 1 then syncrepl enters in the full DB search as
What is your sessionlog setting on each provider for the syncprov overlay?
> For definition purposes I have some memory limitations where I need to
> limit dncachesize for around 80% of DB entrances.
We already went through other things you could do to reduce your memory
footprint in other ways. You've completely ignored that advice. As long
as your dncachesize is in this state, I don't expect things to behave
> I could also note that when in this situation the monitor cache, in a
> very slow pace, changes the cache in a single entrance. Being more
> specific :
> dn: cn=Database 1,cn=Databases,cn=Monitor
> structuralObjectClass: monitoredObject
> createTimestamp: 20090821145848Z
> modifyTimestamp: 20090821145848Z
> monitoredInfo: bdb
> monitorIsShadow: TRUE
> namingContexts: ou=CONTENT,o=domain,c=fr
> readOnly: FALSE
> monitorOverlay: syncprov
> olmBDBEntryCache: 19920
> olmBDBDNCache: 3896287
> olmBDBIDLCache: 2
> olmDbDirectory: /var/openldap-data/bdb1/
> entryDN: cn=Database 1,cn=Databases,cn=Monitor
> subschemaSubentry: cn=Subschema
> hasSubordinates: TRUE
> Stays running in the values 3896287 and 3896288. Looks like the memory
> re-use is being too short causing locks that takes long time causing a non
What value did you set for "cachefree"?
> PS-> I could not put the file in the openldap ftp. It says device full.
> Please let me know how can I send this file.
I've let the maintainer of the system know, hopefully there'll be space
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration