Distributed Index Handler 25.4
Distributed Index Handler Help

# Manage the Indexing Process

To tune indexing performance, you can adjust certain limits on the DIH and its child servers.

- Specify how many times the DIH attempts to send an index action to a child server before it assumes that the connection has failed.

  Set the MaximumRetries configuration parameter (in the [`Server]` section of the DIH configuration file) to the maximum number of attempts. The default value is 10.

- Limit the number of indexing threads that DIH can employ.

  Set the value in the Threads configuration parameter (in the [`Server]` section of the DIH configuration file). The default value is 10 threads. OpenText recommends that you use (1 x Num. CPUs) + 1 spare thread.

- Limit the size of an indexing request string, which limits the amount of data that you can index in a single request.

  Set the MaxInputString configuration parameter (in the [`Server]` section of the DIH configuration file) to the value that you want. The default value is `64000`. A value of `-1` means that there is no limit.

- Specify that DIH must have a certain amount of available disk space for indexing to proceed.

  Set the MinFreeSpaceMB configuration parameter (in the `[Server]` section of the DIH configuration file) to the minimum amount of disk space that DIH must have. By default, DIH must have 20 MB of disk space.

- Specify that a certain number of child servers must be running for indexing to proceed.

  Set the MinChildrenAlive configuration parameter (in the [`Server]` section of the DIH configuration file) to the value that you want. By default, there is no minimum requirement.

- Stop the DIH from turning DREADD actions into DREADDDATA actions.

  Set the PreserveDREADD configuration parameter (in the `[Server]` section of the DIH configuration file) to `True`. This option reduces network load by sending only the path to the IDX file to child servers, rather than streaming all the contents of the IDX file. You can use this parameter only in simple mirror or non-mirror mode. You must ensure that all child servers can access the file system containing the IDX file with the same file path.

- Use weighted indexing to alter the ratio in which documents distribute to different servers in standard distributed mode.

  Set the weight for different servers by using the EngineManagement action with the Weight parameter. For example:

      http://DIHhost:ACIPort/action=EngineManagement&EngineAction=Edit&ID=1&Weight=2

  A server with weight `2` receives twice as many documents as a server with weight `1` and so on. You can set a weight of `0` to add no documents to a server.

- Use round-robin indexing to maximize indexing performance without compromising the Content pool availability. See Round Robin Indexing.

- Use reference-based indexing to distribute the indexing load evenly between Content components. See Reference-Based Indexing.

- Use field-based indexing to distribute the indexing load evenly between Content components. See Field-Based Indexing.

- Use date-based indexing to distribute the indexing load between Content components. See Date-Based Indexing.

Copyright 2025 Open Text
Version 25.4 | Last updated October 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery Distributed Index Handler 25.4

Topic Title: Manage the Indexing Process