Confluence Data Center and Apache Lucene: Asynchronous Indexing Latency

Indexing Behavior in Large-Scale Deployments

Confluence Data Center relies on an inverted index powered by Apache Lucene to facilitate full-text search across pages and attachments. To maintain application responsiveness, the indexing process is handled asynchronously via a background job queue, meaning content updates are not immediately reflected in search results.

In environments with high content volume or large attachments, the gap between a page update and its availability in the Lucene index can vary. This creates a challenge for workflows that require immediate verification of content visibility across distributed shards.

What is the expected behavior for index synchronization across shards during peak CPU utilization? Is there a documented mechanism to prioritize specific content updates within the asynchronous queue to reduce retrieval latency?