JIRA 7.9.x platform upgrade notes

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

Upgrade notes

JIRA administrators

Running JIRA on MySQL

Due to a known bug in MySQL 5.7 we strongly recommend upgrading to MySQL version 5.7.21 or later before upgrading JIRA to versions 7.7 or later.

Connecting to MySQL using IPv6

You can connect JIRA to your MySQL database using an IPv6 address. To do this, complete the following steps to update the URL pattern in your dbconfig.xml file.

  1. Go to <JIRA-install-dir>/bin, and run config.sh or config.bat. This will open the JIRA configuration tool.
  2. In the Database tab, enter the IPv6 address.
  3. Click Save.
  4. Restart JIRA.

You don't have to make any changes if you're sticking to the IPv4 address, or if you're using a hostname for your database.

Connecting to SQL Server 2016

If you'd like to connect to the new supported database, make sure you read about the prerequisite steps: Connecting to SQL Server 2016

Asynchronous cache replication in JIRA Data Center

We’ve changed the way cache is replicated in JIRA Data Center, making the replication asynchronous. Previously, we replicated each modification immediately after it occurred (synchronous). Now, we’re adding each modification to a persistent queue and replicating it to other nodes after it’s promoted to the top of the queue. Thanks to that, replication occurs in the background and is independent of any of your further actions in JIRA.

Tell me more...

This approach improves the scalability of the cluster, and also helps us remove cache inconsistencies between the nodes. After being added to the queue, a modification will remain there until it’s successfully replicated to other nodes. When one of the nodes goes offline, the replication to this node will be stopped, and resumed after the node goes back online again, ensuring that not a single modification gets lost.

Although the replication occurs in the background and is invisible to you and your users, it should slightly increase the disk space needed in the local home directory on each of your nodes. The queued modifications are stored in the local home until they’re successfully replicated. Our tests have shown, however, that a queue typically is 10 MB in total. Mind that there would be a separate queue for each of your nodes.

Plugin developers

See Preparing for JIRA 7.9 for any important changes regarding plugins.

Upgrade procedure

Note: Upgrade to a test environment first. Test your upgrades in your test environment before rolling them into production.

If you're already running a version of JIRA, please follow these instructions to upgrade to the latest version:

  1. Before you upgrade, we strongly recommend that you back up your installation directory, home directory, and database.
  2. Read the release notes and upgrade notes for all releases between your version and the latest version.
  3. Download the latest version of JIRA.
  4. Follow the instructions in the Upgrade Guide.

Upgrading from earlier versions?

  • 7.0, or later
    Take a look at the upgrade matrix. It lists known issues you should be aware of when upgrading between multiple versions.
  • Earlier than 7.0
    Consult the Migration hub. The JIRA 7.0 release introduced significant changes. You must first upgrade to JIRA 7.0 before upgrading to later versions.
Last modified on Jul 11, 2018

Was this helpful?

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