-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.2.0
-
Component/s: Search - Indexing
-
None
-
1
-
Severity 2 - Major
-
9
Problem
After a full site reindex, the task index snapshot is not created. This behavior triggers a full task reindex on all remaining nodes.
Environment
Confluence 9.2
Steps to Reproduce
- Create a Confluence cluster of 2 or more nodes.
- On one node, trigger a full site reindex.
Expected Results
One node should do the reindex job, create a snapshot of the new task index, and the remaining nodes should restore it.
Actual Results
We can see here the reindex finishing up on Node1 and the snapshot being created.
2025-05-20 12:03:33,100 INFO [Caesium-1-4] [report.searchindex.indexmanagement.FullReIndexer] reindexAllTasks Full inline tasks reindexing (for Task Report macro) has been finished. Processed 4672 inline tasks. Duration: 00:00:03.419. In average, 1000 inline tasks were processed in 731 ms.
2025-05-20 12:03:33,129 INFO [Caesium-1-4] [report.searchindex.indexmanagement.TaskReportIndexPersistedStateService] markAsReady Task report index was marked as ready. All task report macros will use search index to retrieve tasks (they will be rendered very fast).
2025-05-20 12:03:38,914 INFO [Caesium-1-1] [impl.system.runner.CreateIndexSnapshotMaintenanceTaskRunner] execute Creating index snapshots. They will then be propagated to other nodes
2025-05-20 12:03:38,967 INFO [Caesium-1-1] [impl.system.runner.CreateIndexSnapshotMaintenanceTaskRunner] execute Index snapshot IndexSnapshot[JournalId=main_index, JournalEntryId=8503] has been created
2025-05-20 12:03:38,987 INFO [Caesium-1-1] [impl.system.runner.CreateIndexSnapshotMaintenanceTaskRunner] execute Index snapshot IndexSnapshot[JournalId=change_index, JournalEntryId=8504] has been created
2025-05-20 12:03:38,987 INFO [Caesium-1-1] [impl.system.runner.CreateIndexSnapshotMaintenanceTaskRunner] execute All index snapshots have been created successfully. Informing other nodes.
See that it processed 4672 inline tasks and created the main and change index snapshots.
If you check the snapshot folder, you will see only the two index snapshots.
At the same time, on the other nodes, we can see it reindex all the tasks again, and restore the main and change index.
2025-05-20 12:03:31,202 INFO [Caesium-1-3] [report.searchindex.indexmanagement.FullReIndexer] reindexAllTasks Inline tasks search index: full reindexing started. While the index is being rebuilt, Task Report macros will temporary use database queries. That means macros will be slower than expected.
...
2025-05-20 12:03:35,715 INFO [Caesium-1-3] [report.searchindex.indexmanagement.FullReIndexer] reindexAllTasks Full inline tasks reindexing (for Task Report macro) has been finished. Processed 4672 inline tasks. Duration: 00:00:04.512. In average, 1000 inline tasks were processed in 965 ms.
2025-05-20 12:03:35,715 DEBUG [Caesium-1-3] [report.searchindex.indexmanagement.TaskReportIndexPersistedStateService] markAsReady Task report index is going to be marked as ready. All task report macros will use search index to retrieve tasks.
2025-05-20 12:03:35,715 INFO [Caesium-1-3] [report.searchindex.indexmanagement.TaskReportIndexPersistedStateService] markAsReady Task report index was marked as ready. All task report macros will use search index to retrieve tasks (they will be rendered very fast).
2025-05-20 12:03:35,716 TRACE [Caesium-1-3] [searchindex.indexmanagement.indexqueue.IndexQueueProcessorImpl] flushQueue Inline task index job flushed 0 tasks. Duration: 00:00:04.515
2025-05-20 12:03:36,199 TRACE [Caesium-1-4] [searchindex.indexmanagement.indexqueue.IndexQueueProcessorImpl] flushQueue Flushing task index queue...
2025-05-20 12:03:36,224 TRACE [Caesium-1-4] [searchindex.indexmanagement.indexqueue.IndexQueueProcessorImpl] flushQueue Inline task index job flushed 0 tasks. Duration: 00:00:00.024
2025-05-20 12:03:40,759 INFO [Caesium-1-4] [impl.system.runner.RestoreIndexSnapshotMaintenanceTaskRunner] doRestore Restoring index snapshots
2025-05-20 12:03:40,872 INFO [Caesium-1-4] [impl.system.runner.RestoreIndexSnapshotMaintenanceTaskRunner] doRestore Index snapshot IndexSnapshot[JournalId=main_index, JournalEntryId=8503] has been restored
2025-05-20 12:03:40,896 INFO [Caesium-1-4] [impl.system.runner.RestoreIndexSnapshotMaintenanceTaskRunner] doRestore Index snapshot IndexSnapshot[JournalId=change_index, JournalEntryId=8504] has been restored
2025-05-20 12:03:40,896 INFO [Caesium-1-4] [impl.system.runner.RestoreIndexSnapshotMaintenanceTaskRunner] doRestore All index snapshots have been restored successfully
This is not optimal and could lead to performance issues, especially for larger instances with multiple nodes and millions of tasks.
Workaround
Copy the index manually to remaining nodes
- Stop node1 (this is where you did the site reindex)
- Compress the index and the journal folders and save them in the shared-home.
Saving these files in the shared home make them available to the other nodes in the cluster.
cd <Confluence Home Dir> tar -cvf <Confluence-shared-home>/node1-index.tar ./index tar -cvf <Confluence-shared-home>/node1-journal.tar ./journal
- Start Confluence on node1 and confirm it is working fine.
Propagating
- Shutdown node2
- On node2 delete the index and journal folders in the local home.
cd <Confluence-home> rm -rf index/ rm -rf journal/
- On node2 uncompress the index and journal folders from the shared home to the local home.
cd <Confluence-home> tar -xvf <Confluence-shared-home>/node1-index.tar tar -xvf <Confluence-shared-home>/node1-journal.tar
- Start Confluence on node2 and confirm it is working fine.
Cleanup
Delete the compressed index and journal files from the shared home folder.
rm -f <Confluence-shared-home>/node1-index.tar rm -f <Confluence-shared-home>/node1-journal.tar
Repeat the process on all remaining nodes.
Notes
- mentioned in
-
Page Loading...