Confluence 7.9 Upgrade Notes

Here are some important notes on upgrading to Confluence 7.9. For details of the new features and improvements in this release, see the Confluence 7.9 Release Notes

On this page:

Upgrade notes 

Change to index architecture

In this release we have made some changes to the Lucene search index to improve performance and stability. One of these changes is to split the index into two parts, a content index and change index. 

Split index upgrade task

When you upgrade to Confluence 7.9, an upgrade task will make two copies of your entire index, remove the relevant content to create the content index and change index, then remove 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. This process will take some time for very large sites.

In our test, it took less than an hour to run the scripts to split a 90 GB index. However, creating the copies of the index prior to this step took just over five hours (on a c5.2xlarge EC2 instance). You may need to give your instance more IOPS.   

Split index upgrade task - clustered Data Center

In addition to the information above, if you run Confluence in a cluster, and there is no index in the local home directory at the point of upgrade, we'll grab the snapshot from the shared home directory and restore that before beginning the upgrade task. Once the upgrade task is complete, we'll generate a new snapshot and save it to the shared home. Subsequent nodes can then grab the snapshot from the shared home, the upgrade task won't need to split the index on every node. 

Journal entry upgrade task

Once the index has been split, another upgrade task will update entries in the journal entry table. This one should only take a few minutes in a large site. You won't be able to use Confluence until both the split index and journal entry upgrade tasks have completed successfully. 

End of support announcements

No end of support announcements at this time. 

Infrastructure changes 

Head to Preparing for Confluence 7.9 to find out more about changes under the hood. 

Known issues

If you encounter a problem during the upgrade and can't solve it, please create a support ticket and one of our support engineers will help you.

Upgrade procedure

Always test the upgrade in a test environment before upgrading in production.

To upgrade Confluence to the latest version:

  1. Go to  > General Configuration > Plan your upgrade and select the version you want to upgrade to. This will run the pre-upgrade checks.
  2. Go to  > General Configuration > Troubleshooting and support tools to check your license validity, application server, database setup and more.
  3. If your version of Confluence is more than one version behind, read the release notes and upgrade guides for all releases between your version and the latest version.
  4. Back up your installation directory, home directory and database.
  5. Download the latest version of Confluence.
  6. Follow the instructions in the Upgrade Guide.

Update configuration files after upgrading

The contents of configuration files such as server.xml, web.xml , setenv.bat / setenv.sh and confluenceinit.properties change from time to time. 

When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation, otherwise you will miss out on any improvements we have made.

Last modified on Oct 30, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.