IBM FileNet P8, Version 5.2.1            

Troubleshooting queues

You can troubleshoot indexing performance by checking the status of the input and output queues.

After monitoring queues, check the queue status in the YourCSSfolder\logs\monitor.csv file.

Table 1. Troubleshooting based on queue status
Queue status Troubleshooting strategy
Input queue is not full
In the monitor.csv file, the input queue size is low relative to the configured input queue size.
Documents are not being received from the client. Ensure that the client is pushing documents fast enough to the server.
Input queue is full, output queue is not full
In the monitor.csv file, the input queue size is high and the output queue size is low, relative to the configured queue sizes.
Check the logs for preprocessing errors and consider increasing the number of preprocessing threads. Low CPU consumption (less than 60%) by the IBM Content Search Services server Java™ process in a large multiprocessor system can also indicate that the number of preprocessing threads should be increased.
A very small number of documents in the input queue indicates that the documents are large. Consider increasing the size of the input queue (along with the heap size).
Both input and output queues are full
In the monitor.csv file, the input and output queue sizes are high, relative to the configured queue sizes.
This queue status is a normal state. Further analysis is required to determine whether there is a problem and how to troubleshoot it (see Monitoring operating system activity for more information). If the analysis indicates that performance is not optimal, you might want to try one or more of the following strategies:
  • Increase the number of indexing threads.
  • Ensure that the disk speed and disk connectivity is fast enough.
  • Configure more frequent, shorter merges by reducing the value of the MaxMergeDocs indexing parameter.
  • Increase the indexing task size (that is, the number of documents that are submitted in a single addOrReplaceDocuments call). Indexing documents in small batches can degrade performance, since the index is flushed and saved to disk for every batch that is indexed. For optimal performance, submit 1000 - 5000 documents in each indexing task.
  • Increase the BufferSize indexing parameter.
  • Reduce the number of collections that are indexed concurrently.


Last updated: March 2016
etsts004.htm

© Copyright IBM Corporation 2016.