Automatic indexing not working
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
- Automatic indexing is not working
- Recently added content will not appear in search results AND/OR activity stream
- Attachment indexing might fail as well
The following appears in the atlassian-confluence.log
2015-10-09 12:09:32,443 ERROR [Indexer: 1] [confluence.search.lucene.ReindexWorkBatch] indexCollection Exception indexing document with id: 7143782
-- referer: http://confluence.XXXXX.com/admin/search-indexes.action | url: /admin/reindex.action | userName: XXX | action: reindex
java.lang.IllegalArgumentException: searchable: Attachment: test.xls v.1 (14419104) <user_name> is not supported: Attachments with minor edit set to true are not accounted for in the change index
at com.atlassian.confluence.search.lucene.tasks.AddChangeDocumentIndexTask.<init>(AddChangeDocumentIndexTask.java:47)
at com.atlassian.confluence.search.lucene.tasks.IndexTaskFactory.createAddChangeDocumentTask(IndexTaskFactory.java:133)
Diagnosis
Environment
- Check if the allocated heap is around 1 GB i.e. Xmx is around 1GB size in the setenv.sh/setenv.bat
Cause
This is caused because the allocated heap is not sufficient for the indexing scheduler and the scheduler does not index Confluence
Note: There won't be any out of memory errors.
Workaround
Increase the heap memory as per the size of the instance.
Please refer the Server hardware requirements guide
Last modified on Nov 2, 2018
Powered by Confluence and Scroll Viewport.