The thing is, each replication agreement runs in a separate thread. These are in addition to the regular operation threads and housekeeping threads. I would suggest no more than 25-30 replication agreements per server, depending on your expected update rate. You can also reduce the number of operation threads (the threadnumber attribute) if you don't expect to have a lot of simultaneous operations against your server. Also, the more processors you have, the more threads you can run. NDS does not scale past 4 processors, though.

Worst case, you will have to have multiple levels of hubs to disperse the replication load. This is quite common.

Aman wrote:

We are using iPlanet Dir Svr 5.0-SP1 and we have 8 suffix/databases.
There are a total of 24 replication agreements currently setup, 3 per
suffix. I am told that there is a limit on the number of replication
agreements that a single directory server can support. Can someone
confirm this ?

We are planning to upgrade to Netscape Directory Server 6.1.1 in the
near future. We intend to have a million entries in the near future
with average entry size being 6K, adding about 12K new entries per day
and support around 100 replication agreements. Can the Netscape
Directory Server handle this ?

Thanks,
Aman




Reply via email to