Folks, I was preparing openLDAP with GDB symbols but looks like the issue was identified and solved in HEAD. Just to identify this issue; was created any sort of ITS for verification in a new load?
Sorry my late response but my baby daughter just born last week and I was having some work at home. I will give a try in the HEAD load. Best Regards, Rodrigo. PS-> Just some link from my daughter http://sites.google.com/site/lauramenina/laura_english --- On Wed, 3/18/09, Howard Chu <[email protected]> wrote: > From: Howard Chu <[email protected]> > Subject: Re: slapd syncrepl consumer having permanent high CPU load > To: "John Morrissey" <[email protected]> > Cc: [email protected] > Date: Wednesday, March 18, 2009, 5:21 AM > John Morrissey wrote: > > After ~16h uptime, slapd with this BDB had increased > its DN cache to ~250k > > entries after it previously appeared stable at the > configured 20k entries, > > and its entry cache had ballooned to ~480k entries. > Its RSS was about 3.6GB > > at this point, with a BDB cache size of 2GB. > > I was finally able to reproduce this (took several hours of > searches. Fortunately I was at a St. Pat's party so I didn't > have to wait around, just got home in time to see it start > going bad...). A fix is now in HEAD. > > (And now we'll see if Guinness is Good For Your Code... ;) > -- -- Howard Chu > CTO, Symas Corp. > http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ >
