This page last changed on Aug 30, 2006 by mryall.

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. While the index is maintained automatically, you may need to rebuild it manually under these circumstances:

  • If you find that your searching and mail threading are malfunctioning.
  • After an upgrade (if a reindex is required after an upgrade, it will be noted in upgrade section of the release notes).

To manually rebuild the content index,

  1. Go to the 'Administration Console' and click on 'Content Indexing' under the heading 'Administration' in the left panel.

    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.

  2. Click 'Rebuild Index'.

Slow reindexing?

Indexing can take a long time to complete, depending on the number of pages, number, type and size of attachments and the amount of memory allocated to Confluence.

It may help to increase the heap memory allocation of Confluence by following these instructions.

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

RELATED TOPICS
Configuring Indexing Language
Content Index Administration
Macro Parameters Index
Working with Macros

!Administration Guide Attachments directory^adminhome.gif!

Any way somebody from Atlassian could list all the screens/lists that rely on the content index to remain up to date to function? This JIRA issue, http://jira.atlassian.com/browse/CONF-6985, seems to suggest that the dashboard's recently updated portlet is also powered by Lucene: not exactly intuitive in my opinion. Knowing which of these non-obvious screens are powered by Lucene would help with troubleshooting out-of-sync issues with the screens (those powered by Lucene can then just be fixed by flushing the content indexing queue or requesting a full re-index).

Posted by oalaoui at Nov 26, 2006 22:56

An exhaustive list would probably fast become inaccurate. The main three places it's used are search (obviously), and lists of recently updated content, including RSS feeds. Some of the label queries are probably (or are likely to become in the future) performed in Lucene as well.

If you have the Confluence source, look for references to the SmartListManager.

Posted by cmiller at Nov 27, 2006 22:04

thanks. I ended up filing a support request to investigate the indexing failures (after getting tired of flushing the indexing queue manually).

Posted by oalaoui at Dec 03, 2006 21:18
Document generated by Confluence on Mar 22, 2007 20:53