The Content Index powers Confluence's search functionality and is also used for a number of related functions such as building email threads in the mail archive, the Space Activity feature and lists of recently-updated content. The Gliffy Plugin also uses the index for some functionality.
For reasons of efficiency, content is not immediately added to the index. New and modified Confluence content is first placed in a queue, and the queue is processed once every minute (by default).
On this page:
To see information about your Confluence instance's content indexing,
Screenshot: Index summary
|
You can ignore the line which says 'Index optimised: NO'. Confluence optimises the index automatically twice a day. The optimised status flag as shown above was really only useful in older versions of Confluence where index optimisation had to happen more frequently due to the type of index format we were using. We'll probably remove this indicator in the next release of Confluence. |
The index is maintained automatically, but you may need to rebuild it manually under circumstances such as these:
To rebuild the content index,
|
Screenshot: Content Indexing
Does the reindexing take a long time to complete? The length of time depends on the following factors:
It may help to increase the heap memory allocation of Confluence by following the instructions in the JIRA documentation.
If you are running an older version of Confluence and find that the index rebuild is not progressing, you may need to shut down Confluence, and restart it with the following Java system property set: bucket.indexing.threads.fixed=1. This will cause the re-indexing to happen in a single thread and be much more stable (but slower).
You can access the Lucene index browser used with Confluence, to see if the required documents have been added to the index.
To view the index browser,
|
Screenshot: Index Browser
The Space Activity feature uses the index to store data. If you remove the index file, the existing activity data will disappear.
