The temporary files that are created for content-based
retrieval activities are not being removed. The accumulation of these
temporary files can cause out-of-disk problems.
Symptoms
The Content Platform Engine server
runs out of disk space. The out-of-disk condition prevents both the
application server and the Content Platform Engine server
from writing to the trace logs.
Causes
When the
Content Platform Engine is
dispatching batches with documents to be indexed, the Oracle® Outside
In Search Export product saves the documents as text as part of the
text extraction process. The text is stored in files in a temporary
work area until the files are indexed by
IBM® Content Search Services. For information about
the location of the temporary work area, see
Setting a work area to optimize text extraction performance.
In
some problem scenarios, such as out-of-memory conditions or Content Platform Engine threads waiting for
the IBM Content Search Services server or
the Oracle® Outside In Search Export product to respond, temporary
text files might remain in the temporary work area. This scenario
can lead to many files being stored in the temporary work area.
Resolving the problem
Restart the
Content Platform Engine server,
which will clean up the temporary work area by removing temporary
files. Restarting the server might take several minutes longer than
normal because of the many temporary files that are being deleted.
For information about how to shut down and start the
Content Platform Engine server, see
Starting and stopping Content Platform Engine.
Consider
moving the temporary work area to a disk that contains approximately
20 GB of space for each Content Platform Engine server.
This size is a guideline only. There are many variables that determine
the configuration, such as: the number of indexing workers (threads),
the batch size, the content being indexed, the size of each content,
and the indexing performance of the IBM Content Search Services servers.