Distribute Data Dynamically across Child Servers
In non-mirror mode, you can configure the DIH to distribute data dynamically across a bank of child servers, based on user-defined limits to the number of documents. This option also allows you to determine when all child servers are full and you require new machines.
NOTE: These options are available in simple non-mirror mode, and in DistributeOnBatch and DistributeSendMinimal modes. They are not available for DistributeByReference, DistributeByDate, or DistributeByFields modes.
To define a maximum for document indexing into child servers, set the MaxDocumentCount
parameter for each child IDOL Server, in the [Server]
section of the IDOL server configuration file. You can also use the MaxDocumentCountUpper
and MaxDocumentCountLower
parameters for more control over the document limits. Refer to the IDOL Server Reference for details on these configuration options.
When an IDOL Server reaches the maximum number of documents, it returns <FULL>
in the GetStatus
action response. IDOL servers also return a <FULL_RATIO>
tag, to indicate how close the index is to being full.
Use the following configuration parameters to specify how the DIH deals with full child servers.
CollectChildFullness |
Whether to send a The DIH then also returns its own fullness information in the response to a |
GetChildStatusMode |
How often to send If you set GetChildStatusMode to |
PingInterval | How often to send GetStatus actions, if you set GetChildStatusMode to ASync . |
RespectChildFullness |
Whether to index into full child servers. If you set this parameter to This implicitly sets CollectChildFullness to |
RespectChildFullnessMaxIndexingGroups |
The maximum number of child server groups to use for indexing. When you set this parameter, DIH indexes into only the first |
If all child servers return <FULL>
, you must either add more machines to your system, or create space on the existing machines.
For more information about these configuration parameters, refer to the DIH Reference.