Startup check: split index migration
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
From Confluence 7.9 the structure of the Lucene search index has changed to enable content and change information to be stored in separate indexes.
This check verifies that upgrade task required to split the index was completed successfully before starting Confluence.
There are a few reasons why this upgrade task may fail in your site:
| Reason | Full error |
|---|---|
Not enough disk space | Your operating system is reporting 100 MB usable free disk space. Confluence needs at least 600 MB to complete the split index migration. If you can’t free up enough disk space, you’ll need to force Confluence to perform a full reindex on startup. |
Can't write to directory | We couldn’t create a directory for the change index. Make sure the user running Confluence can write to <home>/index/change then restart Confluence. |
'Changes' directory already exists | We couldn’t create a directory for the change index because a directory with the same name already exists. Remove the <home>/index/change directory then restart Confluence. |
Problem with the index location or files in index directory | Your configured Lucene index directory <home>/index does not contain a valid Lucene index. Check your index location in the confluence.cfg.xml file. |
To resolve this issue
How you resolve this issue depends on the specific problem.
Not enough disk space
In order to split the index, the upgrade task makes two copies of your entire index, removes the relevant content to create the content index and changes index, then removes the original files. This means you’ll need enough free disk space in your local home directory to temporarily accommodate three copies of your index.
If you’re not able to free up or provision more disk space, you will need to force Confluence to rebuild the index from scratch. See How to Rebuild the Content Indexes From Scratch.
Can’t write to directory
The upgrade task will create a new directory <local-home>/index/change.
The user you are running Confluence as must have permission to:
write to your local home directory
create new directories in your local home directory and sub-directories.
You’ll need to either change the dedicated Confluence user’s permissions, or run Confluence as a different user.
'Change' directory already exists
The upgrade task will create a new directory <local-home>/index/change. It will fail if there is already a directory called 'change' in your index directory.
Move or delete the existing 'change' directory, then restart Confluence to try again.
Problem with the index location or files in index directory
The upgrade task checks that the files in your configured index directory location are valid Lucene index files. If you experience this error, you will need to check:
- that the configured index location has not been changed. To check this go to
<local-home>/confluence-cfg.xmland look for<property name="lucene.index.dir"> - that the index directory does not contain files that should not be there.
If you're unable to work out the source of the problem, you may need to force Confluence to rebuild the index from scratch. See Content Index Administration.
Unexpected error
If you're unable to work out the source of the problem, you may need to force Confluence to rebuild the index from scratch. See Content Index Administration.
What will happen if I dismiss this warning?
You can't start Confluence until you've resolved these issues.