Problem

The Content Indexing UI is unable to detect a reindexing is running when it was initiated at startup. This happens when a rebuild from scratch is being performed.

Steps to Reproduce

1. Stop Confluence on one node
2. Add the following system property:

   confluence.cluster.index.recovery.num.attempts=0
   

3. Delete the index and journal folders from Confluence Home
4. Start the application
5. Visit the Content Indexing page
   The node will take longer than usual to start as it is processing the index.

This behavior is also observed when starting a new node with old index files or without them, as it triggers a full rebuild on the node during startup.

Expected Results

Reindex progress is reported.

Actual Results

No reindex progress is reported on that page.

Workaround

Either follow the progress on the atlassian-confluence-index.log or through the following endpoint:

<Confluence-URL>/json/reindextaskprogress.action

Sample response:

{"total":"1225758","percentageComplete":"91","compactElapsedTime":"00:12:20","count":"1116938"}