Priming or reloading the global indexes from Sun Directory servers

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.

About this task

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 reload-index command. These properties control the rate at which the PingDirectoryProxy 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 doesn’t 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.

To reduce the impact on server performance:

Steps

To reduce the impact of priming on servers, 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.
To specify the amount of time an extended operation response listener can be idle while the global index priming is in progress, use the index-priming-idle-listener-timeout.