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).
The Content Indexes power Confluence's search functionality and 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, 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,
|
スクリーンショット: インデックスの概要
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,
|
|
Screenshot: Content Indexing
インデックス再作成は完了までに長い時間がかかるのでしょうか? 時間の長さは次の要因に依存します。
It may help to increase the heap memory allocation of Confluence by following the instructions in the JIRA documentation.
Confluence の古いバージョンを実行していて、インデックスの再構築が進行していないことを確認した場合、Confluence をシャットダウンし、Java システムプロパティを bucket.indexing.threads.fixed=1 に設定して再起動する必要がある場合があります。これにより、インデックス再作成がシングルスレッドで、安定して実行されるようになります (速度は低下します)。
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.
