Content Manager Content Indexing
In Content Manager Enterprise Studio, right-click on the WorkGroup Server and select Resume to fix the issue.
The DAH (Distributed Action Handler) is used to distributed queries to multiple Content components or IDOL Server, and DIH (Distributed Index Handler) receives index actions (data indexing requests or administrative actions), then distributes them to the connected IDOL servers. These two components can be run in either of the following two modes:
-
mirror mode
-
non-mirror mode
So depending on which mode the DIHs are in, the index requests will be processed accordingly.
In a mirror mode, the DIH sends all the index data that it receives to all the connected IDOL servers. Same index data will be sent to all the connected IDOL servers. So it does not matter whether the index request is sent before or after another request, the DIH will send index data, respectively. Overriding request will never happen in theory. If many requests come at the same time, the DIH processes and puts all the requests in the queue. If many requests come at the same time, the DIH processes them one by one. Basically, the DIH never overrides the requests.
In a non-mirror mode, only difference is the DIH distributes index data evenly across all the connected IDOL servers, not exactly the same to all connected IDOL servers. For example, if the DIH connects to four IDOL servers, it indexes approximately one quarter of the data index into each of the IDOL server. It does not split up sections of individual documents.
If the content to be indexed is huge, make sure that you have a dedicated Workgroup Server for processing content indexing only. If the server is configured for handling other event processor type, say audit events, then the server will be busy addressing the Audit events and the content indexing will not get picked up. The load balancing algorithms rejects it for scheduling content indexing.
As per the design the events will be allocated to a server based on the total event load that already exists on the server(s) in your environment. Therefore, Content Manager recommends to plan and configure the Workgroup Server for event processing, accordingly.