When priming or reloading a global index based on a Sun Directory Server environment, the Sun servers may become overwhelmed and unresponsive because of their method of streaming data. To reduce the impact of priming on these server, you can use the prime-search-entry-per-second property. To reduce the impact of reloading these indexes, use the --searchEntryPerSecond property of the reload-index command. These properties control the rate at which the Directory Proxy Server accepts search result entries from the backend directory servers.

The index-priming-idle-listener-timeout property specifies the amount of time an extended operation response listener can be idle while the global index priming is in progress. For example, if the global index is priming and a backend server stops returning results but does not disconnect, this timeout can be used to force a retry of the operation.

To find the optimum rate, start low and specify a few thousand search entries per second. Then increase as necessary.