Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
Issue Summary
The system administrator should know its mechanism for troubleshooting how index progated in cluster.
There is no technical description about Index Propagation, especially the index propagation will be executed via file system in Shared Home Directory.
This is reproducible on Data Center: yes
Suggest
Add the detail of how index will be propagated in cluster like "via Shared Home Directory", because the system administrator should know its mechanism for troubleshooting how index progated in cluster.
ex: The index files will only be propagated to nodes that have joined the cluster via Shared Home Directory. If Confluence is not running on a node, we won't be able to propagate the index to that node.
Actual Results
Propagate the search index to your cluster
> The index files will only be propagated to nodes that have joined the cluster. If Confluence is not running on a node, we won't be able to propagate the index to that node.
Workaround
Ask Atlassian support
Attachments
Issue Links
- is related to
-
CONFSERVER-81154 Provide the public document regarding the detail of Index Recovery mechanism and specification in cluster
- Gathering Interest
- relates to
-
CONFSERVER-81250 Improve rebuilding index process and Flush System Maintenance Task Queue job for launching of the new node which has no local home like launching via AWS AutoScaling
- Gathering Interest
-
CONFSERVER-81501 Improve the Error message and log level of "LuceneIndexSnapshotException: No snapshot found in shared home for index MAIN_INDEX with journal entry id xx." in JournalSystemMaintenanceTaskQueue
- Gathering Interest