When priming or reloading a global index based on a Sun Directory Server environment, the Sun servers might become overwhelmed and unresponsive because of their method of streaming data.
To reduce the impact of priming and reloading on these servers, use the
prime-search-entry-per-second property and the
--searchEntryPerSecond property of the
command. These properties control the rate at which the Directory Proxy Server accepts search result entries from the backend
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 doesn't disconnect, this timeout can be used to force a retry of
To find the optimum rate, start low and specify a few thousand search entries per second. Then increase as necessary.
To reduce the impact on server performance:
To reduce the impact of priming on servers, use the
To reduce the impact of reloading these indexes, use the
--searchEntryPerSecondproperty of the reload-index command.
To specify the amount of time an extended operation response listener can be idle
while the global index priming is in progress, use the