Cache / Search Index

Ticket Cache

The database index is stored in this cache. The text of each ticket has to be indexed in order to be found during the search in the Request List. The index is also used for the ticket views.

If the index is not yet fully generated or corrupt, the tickets can no longer be displayed correctly. This manifests itself in the fact that newer tickets may be missing and older tickets may still be displayed even though they have already been processed.

The cache is persistent across restarts and can be re-indexed via the Maintenance interface if necessary. The changes will be visible on the user interface after the indexing has been completed. Indexing can take a long time depending on the hardware performance and database connection - but should normally run at about 1000 tickets per minute.