Performance of indexing may degrade over time causing a large backlog of items waiting to be indexed

  • Article ID:100008359
  • Modified Date:
  • Product(s):

Problem

After operating normally for some period, the performance of the indexing service may degrade and not be able to keep up with ingestion rates or respond to search requests in a timely fashion.

Indexer-service.exe processes may consume too much memory and become unresponsive.

 

Cause

The wildcard dictionary is a list of unique words in an individual index volume. This list is updated everytime an item is ingested.  If the size of this dictionary grows too large, the associated index may be unresponsive to search or ingestion requests. 


In the scenario described here, the wildcard dictionary was artificially large due to PGP encrypted attachments being converted to text and sent to the indexing engine.  This caused the indexing engine to add meaningless encrypted strings to the dictionary.  A 1 MB encrypted attachment would add an additional 1 MB of unique words to the dictionary.  This type of data should be excluded from conversion and not sent to the indexing engine.

The size of the wildcard dictionary can be checked by going to the index volume folder on disk (e.g. E:\index2\index1\1BAA95751C944234490D77ABDB567A218_858) and navigating to the live\expansions subfolder.   The wildcard dictionary will be the file without a file extension. 


It is expected this file should generally be under 2 GB.

Solution

This issue has been addressed in the following releases:  


Enterprise Vault 10.0.2 - Release Details
http://www.veritas.com/docs/000011057

 

 

Related Articles

Enterprise Vault 10.0.2 - Release Details

Was this content helpful?

Get Support