The content indexes power Confluence's search functionality. They are 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 them for some of its functionality.

For reasons of efficiency, Confluence does not immediately add content 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:

Viewing the Content Index Summary

To see information about your Confluence instance's content indexing,

  2. Click 'Content Indexing' under the heading 'Administration' in the left-hand panel.

Screenshot: Index summary

Rebuilding the Content Indexes

The content indexes are maintained automatically, but you may need to rebuild one or both of them manually under circumstances such as these:

In new Confluence installations, the 'Did You Mean' feature is not initially activated. To activate it, you first need to build its index by clicking its 'Build' button on this page.

To rebuild either of the content indexes,

  2. Click 'Content Indexing' under the heading 'Administration' in the left-hand panel.
  3. Click the 'Rebuild' button in either the 'Search Index' or 'Did You Mean Index' sections on this page, depending on the particular index you want to rebuild.
  • If one of these indexes has not yet been built, its button will indicate 'Build' instead of 'Rebuild).
  • As shown in the image below, only one index can be (re)built at a time.

Screenshot: Content Indexing

Slow Reindexing

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).

Viewing the Index Browser

Confluence uses a search engine called Lucene. If you need to see more details of the indexed pages in your Confluence site, you can download and run Luke. Luke is a development and diagnostic tool that accesses existing Lucene indexes and allows you to display and modify their content in several ways.

Start Luke and use it to open the index directory, located in your Confluence Home directory. For example:
c:\confluence\data\confluence-home\index.

Confluence 3.2.0 and earlier supplied a JSP page at <Confluence location>/admin/indexbrowser.jsp. You could use the JSP page to access the Lucene index browser used with Confluence and see if the required documents have been added to the index. This JSP page is no longer available in Confluence 3.2.1 and later. If you do have an earlier version of Confluence and are able to access the JSP page, it will prompt for the index you would like to browse. Enter the path of your index directory. By default, this is located at <Confluence Home directory/index>. For example, c:\confluence\data\index.

More Hints and Tips

RELATED TOPICS

administrators guide home