-
Bug
-
Resolution: Fixed
-
Highest
-
6.13.10
-
1
-
Severity 3 - Minor
-
2
-
Issue Summary
Historical versions of attachments are considered as dependants to be re-indexed if their page is updated. This will lead to an issue when new contents cannot be indexed timely and the content index is backing up. The system is also hammered by the huge amount of unnecessary readings from the cache (to check if the versions are indexable) and I/O operations (for deleting the Lucene documents of historical versions of attachments).
Steps to Reproduce
- Move a page that contains thousands of versions of attachments.
- Monitor the journal main_index. It will be updated slowly to keep up with the last journal entry ID in the database.
Expected Results
Only the latest version of attachments on the updated page will be re-indexed.
Actual Results
All Lucene documents of historical versions of attachments are deleted. No new documents for them are added.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-59748] Historical versions of attachments are considered as dependants to be re-indexed when their page is updated
This fix will land in Confluence 7.4.1 which is currently scheduled for 9th of June.
Regards,
James Whitehead
If you're running the Confluence 6.13 Enterprise release, a fix for this issue is now available in Confluence 6.13.12, which you can find in the Download Archives.
A fix for this issue is available to Server and Data Center customers in Confluence 7.5.0
Upgrade now or check out the Release Notes to see what other issues are resolved.
If you're running the Confluence 7.4 Enterprise release, a fix for this issue is now available in Confluence 7.4.1, which you can find in the Download Archives.