Quanah Gibson-Mount wrote:
--On Tuesday, March 02, 2010 7:58 PM +0100 masar...@aero.polimi.it wrote:
25 consumers doing a full refresh probably ate up all threads
available on
the producer. You should either cascade your consumers (build a
replication chain where a layer of consumers acts
--On Wednesday, March 03, 2010 9:05 AM +0900 Jorgen Lundman
lund...@lundman.net wrote:
* Investigate delta-sync
Unknown to me, will need to research if our current ldap software version
can support it. Perhaps try it on the test-servers.
Quite frankly, in the OpenLDAP 2.3 branch, this is
Hello list,
openldap-2.3.41
db-4.2.52.NC-PLUS_5_PATCHES
SunOS ldapmaster01.unix 5.10 Generic_127128-11 i86pc i386 i86pc
We currently have 1 master, and about 25 clients hanging off it, using syncrepl.
Today we restarted the master for the first time in quite some time. This was to
add an
Hello list,
openldap-2.3.41
db-4.2.52.NC-PLUS_5_PATCHES
SunOS ldapmaster01.unix 5.10 Generic_127128-11 i86pc i386 i86pc
We currently have 1 master, and about 25 clients hanging off it, using
syncrepl.
Today we restarted the master for the first time in quite some time. This
was to
add
--On Tuesday, March 02, 2010 7:58 PM +0100 masar...@aero.polimi.it wrote:
25 consumers doing a full refresh probably ate up all threads available on
the producer. You should either cascade your consumers (build a
replication chain where a layer of consumers acts as producers for the
